Multidimensional risk profiling for network access control of mobile devices through a cloud based security system

ABSTRACT

A server configured to profile a mobile device for a cloud-based system, includes a network interface, a data store, and a processor communicatively coupled to one another; and memory storing computer executable instructions, and in response to execution by the processor, the computer-executable instructions cause the processor to, based on communication to a client application on the mobile device, cause the client application to collect data associated with the mobile device; receive the collected data; and determine a device fingerprint and a risk index for the mobile device based on the collected data, wherein the device fingerprint is utilized to uniquely identify the mobile device and the risk index is utilized to manage the mobile device

CROSS-REFERENCE TO RELATED APPLICATION(S)

The present patent/application is a continuation-in-part of U.S. patentapplication Ser. No. 15/153,108 filed May 12, 2016, and entitled“SYSTEMS AND METHODS FOR CLOUD BASED UNIFIED SERVICE DISCOVERY ANDSECURE AVAILABILITY,” the contents of which are incorporated byreference.

The present patent/application is a continuation of U.S. patentapplication Ser. No. 15/377,126 filed Dec. 13, 2016, and entitled“MULTIDIMENSIONAL RISK PROFILING FOR NETWORK ACCESS CONTROL OF MOBILEDEVICES THROUGH A CLOUD BASED SECURITY SYSTEM,” the contents of whichare incorporated by reference.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to computer networking systemsand methods. More particularly, the present disclosure relates tosystems and methods for multidimensional adaptive risk profiling ofmobile devices for policy and access control (Network Access Control(NAC)) through cloud based security systems.

BACKGROUND OF THE DISCLOSURE

There is a staggering growth of endpoint mobile devices in enterprises.With this influx, Information Technology (IT) administrators can nolonger ignore these mobile devices as simply outside their scope ofresponsibility. Correspondingly, there has been an unprecedented growthin the cloud services that are made available by an enterprise to itsemployees. Traditionally, enterprises have deployed one secureapplication for each service for each platform, but this has eventuallyfailed to scale with the growth of mobility in IT. There are myriadnumbers of cloud-based services that are being accessed from unmanagedendpoint mobile devices across diverse operating systems, uncontrollednetwork topologies and vaguely understood mobile geographies. Typically,enterprises have deployed applications for a specific service,applications to access corporate resources that themselves vary fordifferent network conditions, and applications to secure the endpointsitself.

Conventionally, for each application, the enterprise user must performnumerous steps. For example, the end user must contact an enterpriseadministrator (i.e., in person or web portal) to configure the mobiledevice to use the end-point application for a corresponding service. Theend user must enroll in each application to access a service, and theenterprise administrator has to undertake to the complex tasks oftracking, deploying and managing individual apps on each endpoint mobiledevice. Accordingly, it would be advantageous to eliminate the multipleapplications for various enterprise functions, to enable a user toconnect to multiple cloud services.

Normally, to securely access multiple network resources concurrently,the end user has to connect to multiple applications, such as acorporate VPN for accessing enterprise's internal resources (intranet)and a private VPN or a network filtering application for accessinginternet resources. This is not only perplexing for the end user butalso creates several compatibility issues between different applicationswhich compete for network access at different layers of networking. Forinstance, the service of a Virtual Private Network (VPN) application tosecurely connect to an enterprise network is affected by a web securityfirewall application running on the device which monitors and forbidsany network interface changes. The situation is further exacerbated bythe fact that the user needs to reconfigure each application dependingupon the changes in network conditions such as moving from one subnet toanother and that there is no indication to the user to perform such achange. All such service transitions must then be performed manually bythe user with every network change. This is analogous to the situationwhere a user must statically configure Internet Protocol (IP) addressconfiguration on a network interface for every network change. Thisproblem was overcome by Dynamic Host Configuration Protocol (DHCP) thatdiscovers configuration for the interface such as IP Address, SubnetMask, Default Gateways and Domain Name System (DNS) servers. With theadvent of mobility and explosion in the number of cloud services andmobile applications, there is a similar need for unified servicediscovery and secure availability.

Additionally, IT administrators need to restrict mobile devices withhigh risk from network access or sensitive corporate resources toprevent any data breaches or network attack vulnerabilities. Withvisibility into the actual risk of a mobile device, one approach is torestrict access to these sensitive resources from a mobile device.However, it is advantageous and useful to allow network access to mobiledevices to improve productivity.

Conventional Network Access Control (NAC) systems are predominantlystatic and severely limited in scope and implementation. Most NACs areon premise and rely on pre-enrollment static verifications on therequesting mobile device such as anti-virus status, system update level,and configurations. If the mobile device conforms to the business policyand inventory management systems, the access to the network is grantedor denied. This mode of operation blatantly fails for mobile deviceswhich allow users to access network resources from a variety of mobileapplications and network carriers across different geographies where atraditional IT admin has no control. For example, a mobile device maybring malware from any outside network into enterprise network andcontaminate all other network devices.

Further, the systems that NACs employ to profile risk often operate inautonomous isolation and have only limited user/device context thatnotably masks the appraisal of risk. For instance, a malicious userhaving a record of accessing malware applications with a “known”on-premise device may be allowed access to sensitive corporate resourceswithout any advanced security challenge whereas another benign user withan “unknown” mobile device may be disallowed access to a trivialresource or be challenged with some strongest multi-factorauthentication. Also, the IT administrator has to bear theresponsibility of diligently updating NAC servers as new threats emergeto accurately measure the threat profile of the requesting device.

BRIEF SUMMARY OF THE DISCLOSURE

In an exemplary embodiment, a method implemented in a cloud node in acloud based security system for network access control of a mobiledevice based on multidimensional risk profiling thereof includesreceiving posture data from the mobile device; determining a devicefingerprint and a risk index of the mobile device based on the posturedata; and, responsive to a request by the mobile device for networkresources through the cloud based security system, performing amultidimensional risk analysis based on the device fingerprint and therisk index and allowing or denying the request based on themultidimensional risk analysis. The posture data can be obtained from aclient application executed on the mobile device, and wherein the clientapplication communicatively couples the mobile device to the cloud basedsecurity system for network access therethrough. The posture data can beobtained from a client application executed on the mobile device, andwherein the client application can be configured to periodically capturethe posture data comprising hardware parameters, applications installed,versions of the applications, and operating system parameters andpatches. The posture data can include a hash of the information and thereceiving is periodically performed for updates thereto.

The multidimensional risk analysis can include a weighted combination ofdevice risk, application risk, resource risk, user risk, and environmentrisk. The device risk can include risk involved in accessing the networkresource from the mobile device based on the posture data; theapplication risk can include risk involved in using a specificapplication to access the network resource based on the posture data;the resource risk can include potential of the network resource to causedamage; the user risk can include risk based on a user's networkbehavior on the mobile device based on the posture data and based onmonitoring by the cloud based security system; and the environment riskcan include risk assessed by the cloud based security system based ongeolocation and global threat conditions. The weighted combination canbe based on enterprise policy. The risk index for the mobile device canbe updated over time based on network access history and updates to theposture data. Present access can be weighted higher than past access ina weighted combination of risk in the multidimensional risk analysis.The multidimensional risk analysis can determine a risk score associatedwith the request for network resources, and wherein the allowing ordenying the request is based on the risk score.

In another exemplary embodiment, a cloud node in a cloud based securitysystem, configured to provide network access control of a mobile devicebased on multidimensional risk profiling includes a network interface, adata store, and a processor communicatively coupled to one another; andmemory storing computer executable instructions, and in response toexecution by the processor, the computer-executable instructions causethe processor to receive posture data from the mobile device; determinea device fingerprint and a risk index of the mobile device based on theposture data; and, responsive to a request by the mobile device fornetwork resources through the cloud based security system, perform amultidimensional risk analysis based on the device fingerprint and therisk index and allow or deny the request based on the multidimensionalrisk analysis.

In a further exemplary embodiment, a mobile device communicativelycoupled to a cloud based security system which provides network accesscontrol based on multidimensional risk profiling includes a networkinterface, a data store, and a processor communicatively coupled to oneanother; and memory storing computer executable instructions, and inresponse to execution by the processor, the computer-executableinstructions cause the processor to obtain posture data associated withthe mobile device through a client application; provide the posture datato the cloud based security system for determination of a devicefingerprint and a risk index of the mobile device based thereon; andrequest network resources through the cloud based security system viathe client application, wherein the request is allowed or denied by thecloud based security system based on a multidimensional risk analysisbased on the device fingerprint and the risk index.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated and described herein withreference to the various drawings, in which like reference numbers areused to denote like system components/method steps, as appropriate, andin which:

FIG. 1 is a network diagram of a distributed security system;

FIG. 2 is a network diagram of the distributed security system of FIG. 1illustrating various components in more detail;

FIG. 3 is a block diagram of a server which may be used in thedistributed security system of FIG. 1 or with any other cloud-basedsystem;

FIG. 4 is a block diagram of a mobile device which may be used in thesystem of FIG. 1 or with any other cloud-based system;

FIG. 5 is a network diagram of a generalized cloud-based system;

FIG. 6 is a network diagram of a network with a distributed securitycloud providing DNS augmented security;

FIG. 7 is a network diagram of a unified agent application andassociated connectivity and functionality in a network;

FIG. 8 is a network diagram of the workflow of the unified agentapplication in the network of FIG. 7;

FIG. 9 is a flow diagram of an event sequence associated with theunified agent application in the network of FIG. 7;

FIG. 10 is a logical diagram of functional components of the unifiedagent application;

FIG. 11 is a screen shot of a login screen of the unified agentapplication;

FIG. 12 is a screen shot of an admin dashboard for the unified agentapplication;

FIG. 13 is a screen shot of a network evaluation configuration for theunified agent application;

FIG. 14 is a flowchart of a proxy authentication method to the securitycloud;

FIG. 15 is a flowchart of a VPN authentication method to the securitycloud;

FIG. 16 is a flowchart of a device enrollment method for the clientdevice and the unified agent application;

FIG. 17 is a flowchart of a traffic interception method implementedthrough the unified agent application;

FIG. 18 is a flow diagram of traffic interception and splitting usingthe unified agent application;

FIG. 19 is a flow diagram of exemplary functionality of clientapplications, the TUN interface, sockets, and the VPN server for theinterception and splitting using the unified agent application;

FIG. 20 is a flow diagram of tunnel forwarding rules by the unifiedagent application; and

FIG. 21 is a flowchart of a multidimensional risk profiling process forNAC via a cloud based security system and the unified agent application.

DETAILED DESCRIPTION OF THE DISCLOSURE

Again, in various exemplary embodiments, the present disclosure relatesto systems and methods for multidimensional adaptive risk profiling ofmobile devices for policy and access control through cloud basedsecurity systems. The systems and methods solve the problems associatedwith static measures to evaluate risk and proposes a context-awareadaptive risk profiling mechanism for mobile devices from severaldimensions using a cloud based network security system that records themobile device's network usage patterns to take intelligent accesscontrol decisions. Variously, the systems and methods utilize a cloudbased security system coupled with a mobile application (“app”)operating on associated mobile devices. The app is utilized inconjunction with the cloud based security system to employmultidimensional risk profiling of mobile clients. With this riskprofiling, the cloud based security system can provide intelligentaccess control and policy decisions minimizing the security risk andmaximizing the user productivity. Advantageously, a cloud based approachto assess risk eliminates the need to update Network Access Control(NAC) servers with emerging threat information. Based on user risk,access to sensitive resources (such as banking websites or the like) orinternal corporate resources can be denied or supported throughmulti-factor risk-based authentication models. Granular networkquarantine restrictions can be achieved based on the risk level of theuser (mobile device) and the enterprise policy. With a cloud basedapproach to network access control, risk can be correlated universallyfrom multiple perspectives that further accounts for better security.For instance, if an otherwise benign user (mobile device) is trying toaccess an application which was recently accessed by a family ofmalware, the access can be immediately quarantined.

Also, in various exemplary embodiments, the present disclosure relatesto systems and methods for cloud-based unified service discovery andsecure availability. The systems and methods enable a user to connect tomultiple cloud services through the dynamic discovery of availableservices followed by authentication and access as exposed in thecorresponding service protocol. The systems and methods address theunmanageable growth of mobility and cloud-based services which have ledto a proliferation of individual applications for access to individualservices. The systems and method can be implemented through a mobileapplication (“app”) which overcomes the hassle of deploying and managingseveral applications across a gamut of mobile devices, operatingsystems, and mobile networks to gain secure access to the cloud-basedinternet or intranet resources. The mobile application can uniquelyperform a Dynamic evaluation of Network and Service Discovery, UnifiedEnrollment to all services, Application dependent service enablement,Service protocol learning, Service Availability through secure networktraffic forwarding tunnels, and the like.

Again, enterprises have a strong need to provide secure access to cloudservices to its end users. The growth of mobility and cloud in the ITenterprise has made it impossible for IT admins to deploy individualapplications for individual services. The mobile app associated with thesystems and methods overcomes these limitations through the dynamicdiscovery of available services to the end user, followed byauthentication and access to individual services. Further, the mobileapp insightfully learns the protocol for each service and establishes asecure tunnel to the service. In essence, the mobile app is one app thatan enterprise may use to provide secure connectivity to the Internet anddiversified internal corporate applications. At the time of userenrollment, the mobile app will discover all services provided by theenterprise cloud and will enroll the user to all of those services. Itwill then set up secure tunnels for each application depending uponwhether the application is internet bound or if it is internal to thecorporate network (intranet).

The mobile app will also discover all applications provided within theenterprise cloud along with a Global Virtual Private Network (GVPN)service and show the available services to end user. EndpointApplications today provide one service for a specific network function(such as Virtual Private Network (VPN) to a corporate network, websecurity, antivirus to access the Internet). The mobile app can be usedto enable all these services with single enrollment. The mobile app willprovide services to darknet applications along with securing theInternet traffic. The mobile app can set up a local network on themobile device.

§ 1.0 Example High-Level System Architecture—Cloud-Based Security System

Referring to FIG. 1, in an exemplary embodiment, a block diagramillustrates a distributed security system 100. The system 100 may, forexample, be implemented as an overlay network in a wide area network(WAN), such as the Internet, a local area network (LAN), or the like.The system 100 includes processing nodes (PN) 110, that proactivelydetect and preclude the distribution of security threats, e.g., malware,spyware, viruses, email spam, Data Leakage Prevention (DLP), contentfiltering, etc., and other undesirable content sent from or requested byan external system. The processing nodes 110 can also log activity andenforce policies, including logging changes to the various componentsand settings in the system 100. Example external systems may include anenterprise or external system 200, a computer device 220, and a mobiledevice 230, or other network and computing systems communicativelycoupled to the system 100. In an exemplary embodiment, each of theprocessing nodes 110 may include a decision system, e.g., datainspection engines that operate on a content item, e.g., a web page, afile, an email message, or some other data or data communication that issent from or requested by one of the external systems. In an exemplaryembodiment, all data destined for or received from the Internet isprocessed through one of the processing nodes 110. In another exemplaryembodiment, specific data specified by each external system, e.g., onlyemail, only executable files, etc., is process through one of theprocessing node 110.

Each of the processing nodes 110 may generate a decision vector D=[d1,d2, . . . , dn] for a content item of one or more parts C=[c1, c2, . . ., cm]. Each decision vector may identify a threat classification, e.g.,clean, spyware, malware, undesirable content, innocuous, spam email,unknown, etc. For example, the output of each element of the decisionvector D may be based on the output of one or more data inspectionengines. In an exemplary embodiment, the threat classification may bereduced to a subset of categories, e.g., violating, non-violating,neutral, unknown. Based on the subset classification, the processingnode 110 may allow distribution of the content item, precludedistribution of the content item, allow distribution of the content itemafter a cleaning process, or perform threat detection on the contentitem. In an exemplary embodiment, the actions taken by one of theprocessing nodes 110 may be determinative on the threat classificationof the content item and on a security policy of the external system towhich the content item is being sent from or from which the content itemis being requested by. A content item is violating if, for any partC=[c1, c2, . . . , cm] of the content item, at any of the processingnodes 110, any one of the data inspection engines generates an outputthat results in a classification of “violating.”

Each of the processing nodes 110 may be implemented by one or more ofcomputer and communications devices, e.g., server computers, gateways,switches, etc., such as the server 300 described in FIG. 3. In anexemplary embodiment, the processing nodes 110 may serve as an accesslayer 150. The access layer 150 may, for example, provide externalsystem access to the security system 100. In an exemplary embodiment,each of the processing nodes 110 may include Internet gateways and oneor more servers, and the processing nodes 110 may be distributed througha geographic region, e.g., throughout a country, region, campus, etc.According to a service agreement between a provider of the system 100and an owner of an external system, the system 100 may thus providesecurity protection to the external system at any location throughoutthe geographic region.

Data communications may be monitored by the system 100 in a variety ofways, depending on the size and data requirements of the externalsystem. For example, an enterprise 200 may have multiple routers,switches, etc. that are used to communicate over the Internet, and therouters, switches, etc. may be configured to establish communicationsthrough the nearest (in traffic communication time, for example)processing node 110. A mobile device 230 may be configured tocommunicated to a nearest processing node 110 through any availablewireless access device, such as an access point, or a cellular gateway.A single computer device 220, such as a consumer's personal computer,may have its browser and email program configured to access the nearestprocessing node 110, which, in turn, serves as a proxy for the computerdevice 220. Alternatively, an Internet provider may have all of itscustomer traffic processed through the processing nodes 110.

In an exemplary embodiment, the processing nodes 110 may communicatewith one or more authority nodes (AN) 120. The authority nodes 120 maystore policy data for each external system and may distribute the policydata to each of the processing nodes 110. The policy may, for example,define security policies for a protected system, e.g., security policiesfor the enterprise 200. Example policy data may define access privilegesfor users, websites and/or content that is disallowed, restricteddomains, etc. The authority nodes 120 may distribute the policy data tothe processing nodes 110. In an exemplary embodiment, the authoritynodes 120 may also distribute threat data that includes theclassifications of content items according to threat classifications,e.g., a list of known viruses, a list of known malware sites, spam emaildomains, a list of known phishing sites, etc. The distribution of threatdata between the processing nodes 110 and the authority nodes 120 may beimplemented by push and pull distribution schemes described in moredetail below. In an exemplary embodiment, each of the authority nodes120 may be implemented by one or more computer and communicationdevices, e.g., server computers, gateways, switches, etc., such as theserver 300 described in FIG. 3. In some exemplary embodiments, theauthority nodes 120 may serve as an application layer 170. Theapplication layer 170 may, for example, manage and provide policy data,threat data, and data inspection engines and dictionaries for theprocessing nodes 110.

Other application layer functions may also be provided in theapplication layer 170, such as a user interface (UI) front-end 130. Theuser interface front-end 130 may provide a user interface through whichusers of the external systems may provide and define security policies,e.g., whether email traffic is to be monitored, whether certain websitesare to be precluded, etc. Another application capability that may beprovided through the user interface front-end 130 is security analysisand log reporting. The underlying data on which the security analysisand log reporting functions operate are stored in logging nodes (LN)140, which serve as a data logging layer 160. Each of the logging nodes140 may store data related to security operations and network trafficprocessed by the processing nodes 110 for each external system. In anexemplary embodiment, the logging node 140 data may be anonymized sothat data identifying an enterprise is removed or obfuscated. Forexample, identifying data may be removed to provide an overall systemsummary of security processing for all enterprises and users withoutrevealing the identity of any one account. Alternatively, identifyingdata may be obfuscated, e.g., provide a random account number each timeit is accessed, so that an overall system summary of security processingfor all enterprises and users may be broken out by accounts withoutrevealing the identity of any one account. In another exemplaryembodiment, the identifying data and/or logging node 140 data may befurther encrypted, e.g., so that only the enterprise (or user if asingle user account) may have access to the logging node 140 data forits account. Other processes of anonymizing, obfuscating, or securinglogging node 140 data may also be used. Note, as described herein, thesystems and methods for tracking and auditing changes in a multi-tenantcloud system can be implemented in the data logging layer 160, forexample.

In an exemplary embodiment, an access agent 180 may be included in theexternal systems. For example, the access agent 180 is deployed in theenterprise 200. The access agent 180 may, for example, facilitatesecurity processing by providing a hash index of files on a clientdevice to one of the processing nodes 110, or may facilitateauthentication functions with one of the processing nodes 110, e.g., byassigning tokens for passwords and sending only the tokens to aprocessing node so that transmission of passwords beyond the networkedge of the enterprise is minimized. Other functions and processes mayalso be facilitated by the access agent 180. In an exemplary embodiment,the processing node 110 may act as a forward proxy that receives userrequests to external servers addressed directly to the processing node110. In another exemplary embodiment, the processing node 110 may accessuser requests that are passed through the processing node 110 in atransparent mode. A protected system, e.g., enterprise 200, may, forexample, choose one or both of these modes. For example, a browser maybe configured either manually or through the access agent 180 to accessthe processing node 110 in a forward proxy mode. In the forward proxymode, all accesses are addressed to the processing node 110.

In an exemplary embodiment, an enterprise gateway may be configured sothat user requests are routed through the processing node 110 byestablishing a communication tunnel between enterprise gateway and theprocessing node 110. For establishing the tunnel, existing protocolssuch as generic routing encapsulation (GRE), layer two tunnelingprotocol (L2TP), or other Internet Protocol (IP) security protocols maybe used. In another exemplary embodiment, the processing nodes 110 maybe deployed at Internet service provider (ISP) nodes. The ISP nodes mayredirect subject traffic to the processing nodes 110 in a transparentproxy mode. Protected systems, such as the enterprise 200, may use amultiprotocol label switching (MPLS) class of service for indicating thesubject traffic that is to be redirected. For example, at the within theenterprise, the access agent 180 may be configured to perform MPLSlabeling. In another transparent proxy mode exemplary embodiment, aprotected system, such as the enterprise 200, may identify theprocessing node 110 as a next hop router for communication with theexternal servers.

Generally, the distributed security system 100 may generally refer to anexemplary cloud-based security system. Other cloud-based securitysystems and generalized cloud-based systems are contemplated for thesystems and methods for tracking and auditing changes in a multi-tenantcloud system. Cloud computing systems and methods abstract away physicalservers, storage, networking, etc. and instead offer these as on-demandand elastic resources. The National Institute of Standards andTechnology (NIST) provides a concise and specific definition whichstates cloud computing is a model for enabling convenient, on-demandnetwork access to a shared pool of configurable computing resources(e.g., networks, servers, storage, applications, and services) that canbe rapidly provisioned and released with minimal management effort orservice provider interaction. Cloud computing differs from the classicclient-server model by providing applications from a server that areexecuted and managed by a client's web browser, with no installed clientversion of an application required. Centralization gives cloud serviceproviders complete control over the versions of the browser-basedapplications provided to clients, which removes the need for versionupgrades or license management on individual client computing devices.The phrase “software as a service” (SaaS) is sometimes used to describeapplication programs offered through cloud computing. A common shorthandfor a provided cloud computing service (or even an aggregation of allexisting cloud services) is “the cloud.” The distributed security system100 is illustrated herein as one exemplary embodiment of a cloud-basedsystem, and those of ordinary skill in the art will recognize thetracking and auditing systems and methods contemplate operation on anycloud-based system.

§ 2.0 Example Detailed System Architecture and Operation

Referring to FIG. 2, in an exemplary embodiment, a block diagramillustrates various components of the distributed security system 100 inmore detail. Although FIG. 2 illustrates only one representativecomponent processing node 110, authority node 120 and logging node 140,those of ordinary skill in the art will appreciate there may be many ofeach of the component nodes 110, 120 and 140 present in the system 100.A wide area network (WAN) 101, such as the Internet, or some othercombination of wired and/or wireless networks, communicatively couplesthe processing node 110, the authority node 120, and the logging node140 to one another. The external systems 200, 220 and 230 likewisecommunicate over the WAN 101 with each other or other data providers andpublishers. Some or all of the data communication of each of theexternal systems 200, 220 and 230 may be processed through theprocessing node 110.

FIG. 2 also shows the enterprise 200 in more detail. The enterprise 200may, for example, include a firewall (FW) 202 protecting an internalnetwork that may include one or more enterprise servers 216, alightweight directory access protocol (LDAP) server 212, and other dataor data stores 214. Another firewall 203 may protect an enterprisesubnet that can include user computers 206 and 208 (e.g., laptop anddesktop computers). The enterprise 200 may communicate with the WAN 101through one or more network devices, such as a router, gateway, switch,etc. The LDAP server 212 may store, for example, user login credentialsfor registered users of the enterprise 200 system. Such credentials mayinclude user identifiers, login passwords, and a login historyassociated with each user identifier. The other data stores 214 mayinclude sensitive information, such as bank records, medical records,trade secret information, or any other information warranting protectionby one or more security measures.

In an exemplary embodiment, a client access agent 180 a may be includedon a client computer 206. The client access agent 180 a may, forexample, facilitate security processing by providing a hash index offiles on the user computer 206 to a processing node 110 for malware,virus detection, etc. Other security operations may also be facilitatedby the access agent 180 a. In another exemplary embodiment, a serveraccess agent 180 may facilitate authentication functions with theprocessing node 110, e.g., by assigning tokens for passwords and sendingonly the tokens to the processing node 110 so that transmission ofpasswords beyond the network edge of the enterprise 200 is minimized.Other functions and processes may also be facilitated by the serveraccess agent 180 b. The computer device 220 and the mobile device 230may also store information warranting security measures, such aspersonal bank records, medical information, and login information, e.g.,login information to the computers 206 of the enterprise 200, or to someother secure data provider server. The computer device 220 and themobile device 230 can also store information warranting securitymeasures, such as personal bank records, medical information, and logininformation, e.g., login information to a server 216 of the enterprise200, or to some other secure data provider server.

§ 2.1 Example Processing Node Architecture

In an exemplary embodiment, the processing nodes 110 are external tonetwork edges of the external systems 200, 220 and 230. Each of theprocessing nodes 110 stores security policy data 113 received from theauthority node 120 and monitors content items requested by or sent fromthe external systems 200, 220 and 230. In an exemplary embodiment, eachof the processing nodes 110 may also store a detection process filter112 and/or threat data 114 to facilitate the decision of whether acontent item should be processed for threat detection. A processing nodemanager 118 may manage each content item in accordance with the securitypolicy data 113, and the detection process filter 112 and/or threat data114, if stored at the processing node 110, so that security policies fora plurality of external systems in data communication with theprocessing node 110 are implemented external to the network edges foreach of the external systems 200, 220 and 230. For example, depending onthe classification resulting from the monitoring, the content item maybe allowed, precluded, or threat detected. In general, content itemsthat are already classified as “clean” or not posing a threat can beallowed, while those classified as “violating” may be precluded. Thosecontent items having an unknown status, e.g., content items that havenot been processed by the system 100, may be threat detected to classifythe content item according to threat classifications.

The processing node 110 may include a state manager 116A. The statemanager 116A may be used to maintain the authentication and theauthorization states of users that submit requests to the processingnode 110. Maintenance of the states through the state manager 116A mayminimize the number of authentication and authorization transactionsthat are necessary to process a request. The processing node 110 mayalso include an epoch processor 116B. The epoch processor 116B may beused to analyze authentication data that originated at the authoritynode 120. The epoch processor 116B may use an epoch ID to validatefurther the authenticity of authentication data. The processing node 110may further include a source processor 116C. The source processor 116Cmay be used to verify the source of authorization and authenticationdata. The source processor 116C may identify improperly obtainedauthorization and authentication data, enhancing the security of thenetwork. Collectively, the state manager 116A, the epoch processor 116B,and the source processor 116C operate as data inspection engines.

Because the amount of data being processed by the processing nodes 110may be substantial, the detection processing filter 112 may be used asthe first stage of an information lookup procedure. For example, thedetection processing filter 112 may be used as a front end to a lookingof the threat data 114. Content items may be mapped to index values ofthe detection processing filter 112 by a hash function that operates onan information key derived from the information item. The informationkey is hashed to generate an index value (i.e., a bit position). A valueof zero in a bit position in the guard table can indicate, for example,the absence of information, while a one in that bit position canindicate the presence of information. Alternatively, a one could be usedto represent absence, and a zero to represent presence. Each contentitem may have an information key that is hashed. For example, theprocessing node manager 118 may identify the Uniform Resource Locator(URL) address of URL requests as the information key and hash the URLaddress; or may identify the file name and the file size of anexecutable file information key and hash the file name and file size ofthe executable file. Hashing an information key to generate an index andchecking a bit value at the index in the detection processing filter 112generally requires less processing time than actually searching threatdata 114. The use of the detection processing filter 112 may improve thefailure query (i.e., responding to a request for absent information)performance of database queries and/or any general information queries.Because data structures are generally optimized to access informationthat is present in the structures, failure query performance has agreater effect on the time required to process information searches forvery rarely occurring items, e.g., the presence of file information in avirus scan log or a cache where many or most of the files transferred ina network have not been scanned or cached. Using the detectionprocessing filter 112. However, the worst case additional cost is onlyon the order of one, and thus its use for most failure queries saves onthe order of m log m, where m is the number of information recordspresent in the threat data 114.

The detection processing filter 112 thus improves the performance ofqueries where the answer to a request for information is usuallypositive. Such instances may include, for example, whether a given filehas been virus scanned, whether content at a given URL has been scannedfor inappropriate (e.g., pornographic) content, whether a givenfingerprint matches any of a set of stored documents, and whether achecksum corresponds to any of a set of stored documents. Thus, if thedetection processing filter 112 indicates that the content item has notbeen processed, then a worst case null lookup operation into the threatdata 114 is avoided, and a threat detection can be implementedimmediately. The detection processing filter 112 thus complements thethreat data 114 that capture positive information. In an exemplaryembodiment, the detection processing filter 112 may be a Bloom filterimplemented by a single hash function. The Bloom filter may be sparsetable, i.e., the tables include many zeros and few ones, and the hashfunction is chosen to minimize or eliminate false negatives which are,for example, instances where an information key is hashed to a bitposition and that bit position indicates that the requested informationis absent when it is actually present.

§ 2.2 Example Authority Node Architecture

In general, the authority node 120 includes a data store that storesmaster security policy data 123 for each of the external systems 200,220 and 230. An authority node manager 128 may be used to manage themaster security policy data 123, e.g., receive input from users of eachof the external systems defining different security policies and maydistribute the master security policy data 123 to each of the processingnodes 110. The processing nodes 110 then store a local copy of thesecurity policy data 113. The authority node 120 may also store a masterdetection process filter 122. The detection processing filter 122 mayinclude data indicating whether content items have been processed by oneor more of the data inspection engines 116 in any of the processingnodes 110. The authority node manager 128 may be used to manage themaster detection processing filter 122, e.g., receive updates fromprocessing nodes 110 when the processing node 110 has processed acontent item and update the master detection processing filter 122. Forexample, the master detection processing filter 122 may be distributedto the processing nodes 110, which then store a local copy of thedetection processing filter 112.

In an exemplary embodiment, the authority node 120 may include an epochmanager 126. The epoch manager 126 may be used to generateauthentication data associated with an epoch ID. The epoch ID of theauthentication data is a verifiable attribute of the authentication datathat can be used to identify fraudulently created authentication data.In an exemplary embodiment, the detection processing filter 122 may be aguard table. The processing node 110 may, for example, use theinformation in the local detection processing filter 112 to quicklydetermine the presence and/or absence of information, e.g., whether aparticular URL has been checked for malware; whether a particularexecutable has been virus scanned, etc. The authority node 120 may alsostore master threat data 124. The master threat data 124 may classifycontent items by threat classifications, e.g., a list of known viruses,a list of known malware sites, spam email domains, list of known ordetected phishing sites, etc. The authority node manager 128 may be usedto manage the master threat data 124, e.g., receive updates from theprocessing nodes 110 when one of the processing nodes 110 has processeda content item and update the master threat data 124 with any pertinentresults. In some implementations, the master threat data 124 may bedistributed to the processing nodes 110, which then store a local copyof the threat data 114. In another exemplary embodiment, the authoritynode 120 may also monitor the health of each of the processing nodes110, e.g., the resource availability in each of the processing nodes110, detection of link failures, etc. Based on the observed health ofeach of the processing nodes 110, the authority node 120 may redirecttraffic among the processing nodes 110 and/or balance traffic among theprocessing nodes 110. Other remedial actions and processes may also befacilitated by the authority node 120.

§ 2.3 Example Processing Node and Authority Node Communications

The processing node 110 and the authority node 120 may be configuredaccording to one or more push and pull processes to manage content itemsaccording to security policy data 113 and/or 123, detection processfilters 112 and/or 122, and the threat data 114 and/or 124. In a threatdata push implementation, each of the processing nodes 110 stores policydata 113 and threat data 114. The processing node manager 118 determineswhether a content item requested by or transmitted from an externalsystem is classified by the threat data 114. If the content item isdetermined to be classified by the threat data 114, then the processingnode manager 118 may manage the content item according to the securityclassification of the content item and the security policy of theexternal system. If, however, the content item is determined not to beclassified by the threat data 114, then the processing node manager 118may cause one or more of the data inspection engines 117 to perform thethreat detection processes to classify the content item according to athreat classification. Once the content item is classified, theprocessing node manager 118 generates a threat data update that includesdata indicating the threat classification for the content item from thethreat detection process and transmits the threat data update to anauthority node 120.

The authority node manager 128, in response to receiving the threat dataupdate, updates the master threat data 124 stored in the authority nodedata store according to the threat data update received from theprocessing node 110. In an exemplary embodiment, the authority nodemanager 128 may automatically transmit the updated threat data to theother processing nodes 110. Accordingly, threat data for new threats asthe new threats are encountered are automatically distributed to eachprocessing node 110. Upon receiving the new threat data from theauthority node 120, each of processing node managers 118 may store theupdated threat data in the locally stored threat data 114.

In a threat data pull and push implementation, each of the processingnodes 110 stores policy data 113 and threat data 114. The processingnode manager 118 determines whether a content item requested by ortransmitted from an external system is classified by the threat data114. If the content item is determined to be classified by the threatdata 114, then the processing node manager 118 may manage the contentitem according to the security classification of the content item andthe security policy of the external system. If, however, the contentitem is determined not to be classified by the threat data, then theprocessing node manager 118 may request responsive threat data for thecontent item from the authority node 120. Because processing a contentitem may consume valuable resource and time, in some implementations theprocessing node 110 may first check with the authority node 120 forthreat data 114 before committing such processing resources.

The authority node manager 128 may receive the responsive threat datarequest from the processing node 110 and may determine if the responsivethreat data is stored in the authority node data store. If responsivethreat data is stored in the master threat data 124, then the authoritynode manager 128 provide a reply that includes the responsive threatdata to the processing node 110 so that the processing node manager 118may manage the content item in accordance with the security policy data113 and the classification of the content item. Conversely, if theauthority node manager 128 determines that responsive threat data is notstored in the master threat data 124, then the authority node manager128 may provide a reply that does not include the responsive threat datato the processing node 110. In response, the processing node manager 118can cause one or more of the data inspection engines 116 to perform thethreat detection processes to classify the content item according to athreat classification. Once the content item is classified, theprocessing node manager 118 generates a threat data update that includesdata indicating the threat classification for the content item from thethreat detection process and transmits the threat data update to anauthority node 120. The authority node manager 128 can then update themaster threat data 124. Thereafter, any future requests related toresponsive threat data for the content item from other processing nodes110 can be readily served with responsive threat data.

In a detection process filter and threat data push implementation, eachof the processing nodes 110 stores a detection process filter 112,policy data 113, and threat data 114. The processing node manager 118accesses the detection process filter 112 to determine whether thecontent item has been processed. If the processing node manager 118determines that the content item has been processed, it may determine ifthe content item is classified by the threat data 114. Because thedetection process filter 112 has the potential for a false positive, alookup in the threat data 114 may be implemented to ensure that a falsepositive has not occurred. The initial check of the detection processfilter 112, however, may eliminate many null queries to the threat data114, which, in turn, conserves system resources and increasesefficiency. If the content item is classified by the threat data 114,then the processing node manager 118 may manage the content item inaccordance with the security policy data 113 and the classification ofthe content item. Conversely, if the processing node manager 118determines that the content item is not classified by the threat data114, or if the processing node manager 118 initially determines throughthe detection process filter 112 that the content item is not classifiedby the threat data 114, then the processing node manager 118 may causeone or more of the data inspection engines 116 to perform the threatdetection processes to classify the content item according to a threatclassification. Once the content item is classified, the processing nodemanager 118 generates a threat data update that includes data indicatingthe threat classification for the content item from the threat detectionprocess and transmits the threat data update to one of the authoritynodes 120.

The authority node manager 128, in turn, may update the master threatdata 124 and the master detection process filter 122 stored in theauthority node data store according to the threat data update receivedfrom the processing node 110. In an exemplary embodiment, the authoritynode manager 128 may automatically transmit the updated threat data anddetection processing filter to other processing nodes 110. Accordingly,threat data and the detection processing filter for new threats as thenew threats are encountered are automatically distributed to eachprocessing node 110, and each processing node 110 may update its localcopy of the detection processing filter 112 and threat data 114.

In a detection process filter and threat data pull and pushimplementation, each of the processing nodes 110 stores a detectionprocess filter 112, policy data 113, and threat data 114. The processingnode manager 118 accesses the detection process filter 112 to determinewhether the content item has been processed. If the processing nodemanager 118 determines that the content item has been processed, it maydetermine if the content item is classified by the threat data 114.Because the detection process filter 112 has the potential for a falsepositive, a lookup in the threat data 114 can be implemented to ensurethat a false positive has not occurred. The initial check of thedetection process filter 112, however, may eliminate many null queriesto the threat data 114, which, in turn, conserves system resources andincreases efficiency. If the processing node manager 118 determines thatthe content item has not been processed, it may request responsivethreat data for the content item from the authority node 120. Becauseprocessing a content item may consume valuable resource and time, insome implementations the processing node 110 may first check with theauthority node 120 for threat data 114 before committing such processingresources.

The authority node manager 128 may receive the responsive threat datarequest from the processing node 110 and may determine if the responsivethreat data is stored in the authority node data 120 store. Ifresponsive threat data is stored in the master threat data 124, then theauthority node manager 128 provides a reply that includes the responsivethreat data to the processing node 110 so that the processing nodemanager 118 can manage the content item in accordance with the securitypolicy data 112 and the classification of the content item, and furtherupdate the local detection processing filter 112. Conversely, if theauthority node manager 128 determines that responsive threat data is notstored in the master threat data 124, then the authority node manager128 may provide a reply that does not include the responsive threat datato the processing node 110. In response, the processing node manager 118may cause one or more of the data inspection engines 116 to perform thethreat detection processes to classify the content item according to athreat classification. Once the content item is classified, theprocessing node manager 118 generates a threat data update that includesdata indicating the threat classification for the content item from thethreat detection process and transmits the threat data update to anauthority node 120. The authority node manager 128 may then update themaster threat data 124. Thereafter, any future requests for related toresponsive threat data for the content item from other processing nodes110 can be readily served with responsive threat data.

The various push and pull data exchange processes provided above areexemplary processes for which the threat data and/or detection processfilters may be updated in the system 100 of FIGS. 1 and 2. Other updateprocesses, however, are contemplated herein. The data inspection engines116, processing node manager 118, authority node manager 128, userinterface manager 132, logging node manager 148, and authority agent 180may be realized by instructions that upon execution cause one or moreprocessing devices to carry out the processes and functions describedabove. Such instructions can, for example, include interpretedinstructions, such as script instructions, e.g., JavaScript orECMAScript instructions, or executable code, or other instructionsstored in a non-transitory computer readable medium. Other processingarchitectures can also be used, e.g., a combination of speciallydesigned hardware and software, for example.

§ 3.0 Exemplary Server Architecture

Referring to FIG. 3, in an exemplary embodiment, a block diagramillustrates a server 300 which may be used in the system 100, in othersystems, or standalone. Any of the processing nodes 110, the authoritynodes 120, and the logging nodes 140 may be formed through one or moreservers 300. Further, the computer device 220, the mobile device 230,the servers 208, 216, etc. may include the server 300 or similarstructure. The server 300 may be a digital computer that, in terms ofhardware architecture, generally includes a processor 302, input/output(I/O) interfaces 304, a network interface 306, a data store 308, andmemory 310. It should be appreciated by those of ordinary skill in theart that FIG. 3 depicts the server 300 in an oversimplified manner, anda practical embodiment may include additional components and suitablyconfigured processing logic to support known or conventional operatingfeatures that are not described in detail herein. The components (302,304, 306, 308, and 310) are communicatively coupled via a localinterface 312. The local interface 312 may be, for example, but notlimited to, one or more buses or other wired or wireless connections, asis known in the art. The local interface 312 may have additionalelements, which are omitted for simplicity, such as controllers, buffers(caches), drivers, repeaters, and receivers, among many others, toenable communications. Further, the local interface 312 may includeaddress, control, and/or data connections to enable appropriatecommunications among the aforementioned components.

The processor 302 is a hardware device for executing softwareinstructions. The processor 302 may be any custom made or commerciallyavailable processor, a central processing unit (CPU), an auxiliaryprocessor among several processors associated with the server 300, asemiconductor-based microprocessor (in the form of a microchip or chipset), or generally any device for executing software instructions. Whenthe server 300 is in operation, the processor 302 is configured toexecute software stored within the memory 310, to communicate data toand from the memory 310, and to generally control operations of theserver 300 pursuant to the software instructions. The I/O interfaces 304may be used to receive user input from and/or for providing systemoutput to one or more devices or components. User input may be providedvia, for example, a keyboard, touchpad, and/or a mouse. System outputmay be provided via a display device and a printer (not shown). I/Ointerfaces 304 may include, for example, a serial port, a parallel port,a small computer system interface (SCSI), a serial ATA (SATA), a fibrechannel, Infiniband, iSCSI, a PCI Express interface (PCI-x), an infrared(IR) interface, a radio frequency (RF) interface, and/or a universalserial bus (USB) interface.

The network interface 306 may be used to enable the server 300 tocommunicate over a network, such as the Internet, the WAN 101, theenterprise 200, and the like, etc. The network interface 306 mayinclude, for example, an Ethernet card or adapter (e.g., 10BaseT, FastEthernet, Gigabit Ethernet, 10 GbE) or a wireless local area network(WLAN) card or adapter (e.g., 802.11a/b/g/n). The network interface 306may include address, control, and/or data connections to enableappropriate communications on the network. A data store 308 may be usedto store data. The data store 308 may include any of volatile memoryelements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM,and the like)), nonvolatile memory elements (e.g., ROM, hard drive,tape, CDROM, and the like), and combinations thereof. Moreover, the datastore 308 may incorporate electronic, magnetic, optical, and/or othertypes of storage media. In one example, the data store 1208 may belocated internal to the server 300 such as, for example, an internalhard drive connected to the local interface 312 in the server 300.Additionally, in another embodiment, the data store 308 may be locatedexternal to the server 300 such as, for example, an external hard driveconnected to the I/O interfaces 304 (e.g., SCSI or USB connection). In afurther embodiment, the data store 308 may be connected to the server300 through a network, such as, for example, a network attached fileserver.

The memory 310 may include any of volatile memory elements (e.g., randomaccess memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatilememory elements (e.g., ROM, hard drive, tape, CDROM, etc.), andcombinations thereof. Moreover, the memory 310 may incorporateelectronic, magnetic, optical, and/or other types of storage media. Notethat the memory 310 may have a distributed architecture, where variouscomponents are situated remotely from one another, but can be accessedby the processor 302. The software in memory 310 may include one or moresoftware programs, each of which includes an ordered listing ofexecutable instructions for implementing logical functions. The softwarein the memory 310 includes a suitable operating system (O/S) 314 and oneor more programs 316. The operating system 314 essentially controls theexecution of other computer programs, such as the one or more programs316, and provides scheduling, input-output control, file and datamanagement, memory management, and communication control and relatedservices. The one or more programs 316 may be configured to implementthe various processes, algorithms, methods, techniques, etc. describedherein.

§ 4.0 Exemplary Mobile Device Architecture

Referring to FIG. 4, in an exemplary embodiment, a block diagramillustrates a mobile device 400, which may be used in the system 100 orthe like. The mobile device 400 can be a digital device that, in termsof hardware architecture, generally includes a processor 402,input/output (I/O) interfaces 404, a radio 406, a data store 408, andmemory 410. It should be appreciated by those of ordinary skill in theart that FIG. 4 depicts the mobile device 400 in an oversimplifiedmanner, and a practical embodiment may include additional components andsuitably configured processing logic to support known or conventionaloperating features that are not described in detail herein. Thecomponents (402, 404, 406, 408, and 402) are communicatively coupled viaa local interface 412. The local interface 412 can be, for example, butnot limited to, one or more buses or other wired or wirelessconnections, as is known in the art. The local interface 412 can haveadditional elements, which are omitted for simplicity, such ascontrollers, buffers (caches), drivers, repeaters, and receivers, amongmany others, to enable communications. Further, the local interface 412may include address, control, and/or data connections to enableappropriate communications among the aforementioned components.

The processor 402 is a hardware device for executing softwareinstructions. The processor 402 can be any custom made or commerciallyavailable processor, a central processing unit (CPU), an auxiliaryprocessor among several processors associated with the mobile device400, a semiconductor-based microprocessor (in the form of a microchip orchip set), or generally any device for executing software instructions.When the mobile device 400 is in operation, the processor 402 isconfigured to execute software stored within the memory 410, tocommunicate data to and from the memory 410, and to generally controloperations of the mobile device 400 pursuant to the softwareinstructions. In an exemplary embodiment, the processor 402 may includean optimized mobile processor such as optimized for power consumptionand mobile applications. The I/O interfaces 404 can be used to receiveuser input from and/or for providing system output. User input can beprovided via, for example, a keypad, a touch screen, a scroll ball, ascroll bar, buttons, barcode scanner, and the like. System output can beprovided via a display device such as a liquid crystal display (LCD),touch screen, and the like. The I/O interfaces 404 can also include, forexample, a serial port, a parallel port, a small computer systeminterface (SCSI), an infrared (IR) interface, a radio frequency (RF)interface, a universal serial bus (USB) interface, and the like. The I/Ointerfaces 404 can include a graphical user interface (GUI) that enablesa user to interact with the mobile device 400. Additionally, the I/Ointerfaces 404 may further include an imaging device, i.e. camera, videocamera, etc.

The radio 406 enables wireless communication to an external accessdevice or network. Any number of suitable wireless data communicationprotocols, techniques, or methodologies can be supported by the radio406, including, without limitation: RF; IrDA (infrared); Bluetooth;ZigBee (and other variants of the IEEE 802.15 protocol); IEEE 802.11(any variation); IEEE 802.16 (WiMAX or any other variation); DirectSequence Spread Spectrum; Frequency Hopping Spread Spectrum; Long TermEvolution (LTE); cellular/wireless/cordless telecommunication protocols(e.g. 3G/4G, etc.); wireless home network communication protocols;paging network protocols; magnetic induction; satellite datacommunication protocols; wireless hospital or health care facilitynetwork protocols such as those operating in the WMTS bands; GPRS;proprietary wireless data communication protocols such as variants ofWireless USB; and any other protocols for wireless communication. Thedata store 408 may be used to store data. The data store 408 may includeany of volatile memory elements (e.g., random access memory (RAM, suchas DRAM, SRAM, SDRAM, and the like)), nonvolatile memory elements (e.g.,ROM, hard drive, tape, CDROM, and the like), and combinations thereof.Moreover, the data store 408 may incorporate electronic, magnetic,optical, and/or other types of storage media.

The memory 410 may include any of volatile memory elements (e.g., randomaccess memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatilememory elements (e.g., ROM, hard drive, etc.), and combinations thereof.Moreover, the memory 410 may incorporate electronic, magnetic, optical,and/or other types of storage media. Note that the memory 410 may have adistributed architecture, where various components are situated remotelyfrom one another, but can be accessed by the processor 402. The softwarein memory 410 can include one or more software programs, each of whichincludes an ordered listing of executable instructions for implementinglogical functions. In the example of FIG. 4, the software in the memory410 includes a suitable operating system (O/S) 414 and programs 416. Theoperating system 414 essentially controls the execution of othercomputer programs and provides scheduling, input-output control, fileand data management, memory management, and communication control andrelated services. The programs 416 may include various applications,add-ons, etc. configured to provide end user functionality with themobile device 400. For example, exemplary programs 416 may include, butnot limited to, a web browser, social networking applications, streamingmedia applications, games, mapping and location applications, electronicmail applications, financial applications, and the like. In a typicalexample, the end user typically uses one or more of the programs 416along with a network such as the system 100.

§ 5.0 Exemplary General Cloud System

Referring to FIG. 5, in an exemplary embodiment, a cloud system 500 isillustrated for implementing the systems and methods described hereinfor tracking and auditing changes in a multi-tenant cloud system. Thecloud system 500 includes one or more cloud nodes (CN) 502communicatively coupled to the Internet 504. The cloud nodes 502 mayinclude the processing nodes 110, the server 300, or the like. That is,the cloud system 500 may include the distributed security system 100 oranother implementation of a cloud0based system, such as a systemproviding different functionality from security. In the cloud system500, traffic from various locations (and various devices locatedtherein) such as a regional office 510, headquarters 520, variousemployee's homes 530, mobile laptop 540, and mobile device 542communicates to the cloud through the cloud nodes 502. That is; each ofthe locations 510, 520, 530, 540, 542 is communicatively coupled to theInternet 504 through the cloud nodes 502. For security, the cloud system500 may be configured to perform various functions such as spamfiltering, uniform resource locator (URL) filtering, antivirusprotection, bandwidth control, data loss prevention, zero-dayvulnerability protection, web 2.0 features, and the like. In anexemplary embodiment, the cloud system 500 and the distributed securitysystem 100 may be viewed as Security-as-a-Service through the cloud. Ingeneral, the cloud system 500 can be configured to perform any functionin a multi-tenant environment. For example, the cloud system 500 canprovide content, a collaboration between users, storage, applicationhosting, and the like.

In an exemplary embodiment, the cloud system 500 can utilize the systemsand methods for tracking and auditing changes in a multi-tenant cloudsystem. That is, the cloud system 500 can track and audit administratoractivity associated with the cloud system 500 in a segregated andoverlaid fashion from the application functions performed by the cloudsystem 500. This segregated and overlaid fashion decouples the trackingand auditing from application logic, maximizing resources and minimizingdevelopment complexity and runtime processing. The cloud system 500 (andthe system 100) can be offloaded from complex tracking and auditingfunctions so that it can provide its primary function. In the context ofa distributed security system, the tracking and auditing systems andmethods enable accountability, intrusion detection, problem diagnosis,and data reconstruction, all in an optimized fashion considering theexponential growth in cloud-based systems.

§ 6.0 DNS Augmented Security

In an exemplary embodiment, the cloud system 500 and/or the distributedsecurity system 100 can be used to perform DNS surrogation.Specifically, DNS surrogation can be a framework for distributed orcloud-based security/monitoring as is described herein. Endpointsecurity is no longer effective as deployments move to the cloud withusers accessing content from a plurality of devices in an anytime,anywhere connected manner. As such, cloud-based security is the mosteffective means to ensure network protection where different devices areused to access network resources. Traffic inspection in the distributedsecurity system 100 and the cloud-based system 500 is performed in anin-line manner, i.e. the processing nodes 110 and the cloud nodes 502are in the data path of connecting users. Another approach can include apassive approach to the data path. DNS is one of the most fundamental IPprotocols. With DNS surrogation as a technique, it is proposed to useDNS for dynamic routing of traffic, per-user authentication and policyenforcement, and the like.

In conjunction with the cloud system 500 and/or the distributed securitysystem 100, various techniques can be used for monitoring which isdescribed on a sliding scale between always inline to never inline.First, in an always inline manner, all user traffic is between inlineproxies such as the processing nodes 110 or the cloud nodes 502 withoutexception. Here, DNS can be used as a forwarding mechanism to the inlineproxies. Second, in a somewhat always inline manner, all user trafficexcept for certain business partners or third parties is between inlineproxies such as the processing nodes 110 or the cloud nodes 502. Third,in an inline manner for most traffic, high bandwidth applications can beconfigured to bypass the inline proxies such as the processing nodes 110or the cloud nodes 502. Exemplary high bandwidth applications caninclude content streaming such as video (e.g., Netflix, Hulu, YouTube,etc.) or audio (e.g., Pandora, etc.). Fourth, in a mixed manner, inlinemonitoring can be used for “interesting” traffic as determined bysecurity policy with other traffic being direct. Fifth, in an almostnever inline manner, simple domain-level URL filtering can be used todetermine what is monitored inline. Finally, sixth, in a never inlinemanner, DNS augmented security can be used.

Referring to FIG. 6, in an exemplary embodiment, a network diagramillustrates a network 550 with a distributed security cloud 552providing DNS augmented security. The network 550 includes a user device554 connecting to the distributed security cloud 552 via an anycast DNSserver 556. The anycast DNS server 556 can be a server such as theserver 300 of FIG. 3. Also, the anycast DNS server 556 can be theprocessing node 110, the cloud node 502, etc. The distributed securitycloud 552 includes the anycast DNS server 556, policy data 558, and aninline proxy 560. The inline proxy 560 can include the processing node110, the cloud node 502, etc. In operation, the user device 554 isconfigured with a DNS entry of the anycast DNS server 556, and theanycast DNS server 556 can perform DNS surrogation as is describedherein. The distributed security cloud 552 utilizes the anycast DNSserver 556, the policy data 558, and the inline proxy 560 to perform theDNS augmented security.

The network 550 illustrates the DNS augmented security where DNSinformation is used as follows. First, at step 562, the user device 554requests a DNS lookup of a site, e.g. “what is the IP address ofsite.com?” from the anycast DNS server 556. The anycast DNS server 556accesses the policy data 558 to determine the policy associated with thesite at step 564. The anycast DNS server 556 returns the IP address ofthe site based on the appropriate policy at step 566. The policy data558 determines if the site either goes direct (step 568) to theInternet, is inspected by the inline proxy (step 570), or is blocked perpolicy (step 572). Here, the anycast DNS server 556 returns the IPaddress with additional information if the site is inspected or blocked.For example, if the anycast DNS server 556 determines the access isdirect, the anycast DNS server 556 simply returns the IP address of thesite. If the anycast DNS server 556 determines the site is blocked orinspected, the anycast DNS server 556 returns the IP address to theinline proxy 560 with additional information. The inline proxy 560 canblock the site or provide fully in line proxied traffic to the site(step 574) after performing monitoring for security.

The DNS augmented security advantageously is protocol and applicationagnostic providing visibility and control across virtually allInternet-bound traffic. For example, DNS-based protocols includeInternet Relay Chat (IRC), Session Initiation Protocol (SIP), HypertextTransfer Protocol (HTTP), HTTP Secure (HTTPS), Post Office Protocol v3(POP3), Internet Message Access Protocol (IMAP), etc. Further, emergingthreats are utilizing DNS today especially Botnets and advancedpersistent threats (APTs). For example, Fast flux is a DNS techniqueused to hide phishing and malware delivery sites behind an ever-changingnetwork of compromised hosts acting as proxies. The DNS augmentedsecurity provides deployment flexibility when full inline monitoring isnot feasible. For example, this can be utilized in highly distributedwith high bandwidth environments, in locations with challenging InternetAccess, etc. The DNS augmented security can provide URL filtering,white/black list enforcement, etc. for enhanced security without contentfiltering. In this manner, the network 550 can be used with thedistributed security system 100 and the cloud system 500 to providecloud-based security without requiring full inline connectivity.

§ 7.0 Unified Agent Application

Referring to FIG. 7, in an exemplary embodiment, a network diagramillustrates a unified agent application 600 and associated connectivityand functionality in a network 602. The unified agent application 600 isexecuted on a mobile device 604. The unified agent application 600dynamically learns all available services, adapts to changing networkenvironments, and provides a seamless and a secure network resourceaccess to Internet and darknet hosted applications. This is achievedthrough dynamic evaluation of network conditions, enrollment toindividual services, learning individual service protocols, creating alink-local network on the device 604, and establishing multiple securetunnels to cloud services over this local network.

The unified agent application 600 is communicatively coupled to an agentmanager cloud 606, and a security cloud 608. Note, the security cloud608 can be the distributed security system 100, the cloud system 500,the distributed security cloud 552, etc. The unified agent application600 enables communication to enterprise private resources 612 via thesecurity cloud 608 and to the Internet 504 via the security cloud 608.The agent manager cloud 606 can communicate with enterprise assetmanagement 614, an enterprise Security Assertion Markup Language (SAML)Identity provider (IDP) 616, and an enterprise Certificate Authority(CA) 618. The device 604 and the unified agent application 600 canperform a registration/identity 620 process through the agent managercloud 606 where the user identity, the user's certificates, and a devicefingerprint can uniquely identify the device 604. Once registered, theunified agent application 600 has an identity 622 which can include theuser, certificates, device posture, etc. and which is shared with thesecurity cloud 608.

The unified agent application 600 operates on a client-server modelwhere an IT admin enables appropriate services for end users at a CloudAdministration Server (CAS) which can be part of an agent manager cloud606, namely the enterprise asset management 614. Every client can make aunicast request to the agent manager cloud 606 (e.g., CAS) to discoverall enabled services. On acknowledging the response, the client issues arequest to authenticate to each service's cloud Identity Providers, theenterprise SAML IDP 616. Authentication can be multi-factor dependingupon the nature of the service. On successful authentication, servercontacts Mobile Device Management (MDM) or Inventory management providerto define access control rights for the device 604. Post authorization,the device 604 is successfully enrolled into the agent manager cloud 606which tracks and monitors all behavior of the device 604.

Post-enrollment, the device 604 creates a link local network with aspecific IP configuration, opens a virtual network interface to read andwrite packets and opens multiple listening sockets at custom ports tocreate secure tunnels to available services through the security cloud608. On network changes, the device 604 dynamically evaluatesreachability to preconfigured domains and depending upon the result itappropriately transitions all network tunnels, thus providing a seamlessexperience to the end user. Further, the device 604 also intelligentlylearns the conditions which are appropriate for setting up networktunnels to cloud services depending upon several network heuristics suchas reachability to a particular cloud service.

§ 7.1 Unified Agent Application—Functionality

Generally, the unified agent application 600 support two broadfunctional categories—1) dynamic service discovery and access controlsand 2) service availability. The dynamic service discovery and accesscontrols include service configuration by the administrator, servicediscovery by the device 604, service acknowledgment and authentication,service authorization and enrollment, and the like. For serviceconfiguration by the administrator, the IT admin can provide cloudservice details at a centralized knowledge server, such as part of theagent manager cloud 606, the enterprise asset management 614, etc. Thecloud service details include the service type (e.g.,Internet/intranet), network protocol, identity provider, server address,port and access controls, etc.

For service discovery by the device 604, the device 604 can issue anetwork request to a known Cloud Administrative Server (CAS) in theagent manager cloud 606 to discover all enabled services for a user. Ifa specific cloud server is not known a priori, the device 604 canbroadcast the request to multiple clouds, e.g., through the agentmanager cloud 606 communicating to the enterprise asset management 614,the enterprise SAML IDP 616, and the enterprise CA 618.

For the service acknowledgment and authentication, the device 604acknowledges the response of service discovery and initiates theauthentication flow. The device 604 learns the authentication protocolthrough the service discovery configuration and performs authenticationof a configured nature at the enterprise SAML IDP 616. For the serviceauthorization and enrollment, post successful authentication, the CAS,authorizes the device 604 and fetches the access control information bycontacting an MDM/Inventory Solutions Provider. Depending on the usercontext and the nature of access, the CAS enrolls the device 604 intoseveral cloud services and informs the cloud services that the user hasbeen enrolled for access.

The service availability includes link local network setup, a trafficinterceptor, and dynamic traffic forwarding tunnels to authorizedservices. The link local network setup, post enrollment, has the device604 create a local network on the device 604 itself to manage variousnetworking functionalities. For the traffic interceptor, the device 604intercepts and evaluates all Internet traffic. Allowed traffic istunneled to the cloud services such as in the security cloud 608 whereasrest of the traffic is denied as per enterprise policies. For thedynamic traffic forwarding tunnels to authorized services, dependingupon the evaluation, the device 604 splits the traffic into thedifferent tunnel to individual cloud services such as in the securitycloud 608.

The unified agent application 600 is a single application that providessecurity connectivity to the Internet 504 and darknet hostedapplications, such as the enterprise private resources 612. The unifiedagent application 600 communicates securely to the agent manager 606which is controlled by an IT admin. The unified agent application 600learns available services and authenticates with each service. Postproper enrollment, the unified agent application 600 securely connectsto cloud services by means of network tunnels.

§ 7.2 Unified Agent Application—Workflow

Referring to FIG. 8, in an exemplary embodiment, a network diagramillustrates the workflow of the unified agent application 600 in thenetwork 602. The device 604 again executes the unified agent application600, as well as a browser 630 (or some other application requestingnetwork services). FIG. 8 illustrates exemplary workflow. First, thedevice 604 includes authentication through an application portal 632 anddownload/install of the unified agent application 600 therefrom (step640-1). Note, the application portal 632 can be a website, Apple's appstore, Google play, Windows store, etc. Once installed, the unifiedagent application 600 communicates to the agent manager cloud 606communicating identity and asking for available services (“I am User X,what are my services?”) and the agent manager cloud 606 responds withthe available services (“You have Z services”) (step 640-2).

Next, the unified agent application 600 includes authentication using aVPN Service Provider (SP) with the security cloud 608 (step 640-3). Theunified agent application 600 next enrolls the device 604 through theagent manager cloud 606 (step 640-4). The agent manager cloud 606performs a device asset policy check with the enterprise assetmanagement 614 (step 640-5). The agent manager cloud 606, uponsuccessful check, provides the unified agent application 600 anaffirmative response (step 640-6). The unified agent application 600sends a Certificate Signing Request (CSR) to the agent manager cloud 606(step 640-7) and the agent manager cloud 606 sends the CSR request tothe enterprise CA and the certificate is returned to the unified agentapplication 600 (step 640-8). Finally, the unified agent application 600enables VPN connectivity to the security cloud 608 (step 640-9).

Referring to FIG. 9, in an exemplary embodiment, a flow diagramillustrates an event sequence associated with the unified agentapplication 600 in the network 602. The event sequence is shown betweenthe device 604 executing the unified agent application 600, a mobileadmin function 650 such as implemented through the agent manager cloud606, a cloud node 502, a VPN node 652 such as through the security cloud608, a MDM function 654 such as through the enterprise asset management614, and an IDP function 656 such as through the enterprise SAML IDP616. The device 604 discovers services with the mobile admin function650 (step 660), and the device 604 is authenticated by the IDP function656 (step 662). The device 604 enrolls in discovered services throughthe mobile admin function 650 (step 664).

The mobile admin function 650 is configured to authorize the serviceswith the MDM function 654 (step 666) enroll in the services through theVPN node 652 (step 668) and the processing nodes 110/cloud nodes 502(step 670). A success/error is provided by the mobile admin function 650to the device 604. Subsequently, the device 604, through the unifiedagent application 600, accesses the services such as a secure tunnel forinternet access through the processing nodes 110/cloud nodes 502 (step674) or a secure tunnel for intranet access through the VPN node 652(step 676).

§ 7.3 Unified Agent Application—Architecture

Referring to FIG. 10, in an exemplary embodiment, a logical diagramillustrates functional components of the unified agent application 600.The unified agent application 600 is configured to operate on the mobiledevice 604. The security cloud 608, e.g., through the distributedsecurity system 100 or the cloud system 500, provides Internet securityas well as cloud-based remote access to enterprise internal resources,through a VPN. These cloud services are designed and well suited forroad warriors. Road warriors are the users who are accessing Internetand enterprise internal services from outside the corporate physicalnetwork perimeter, i.e., the mobile laptop 540 and/or the mobile device542 in the cloud system 500. These are the users who are accessingInternet and Enterprise resources from home, airports, coffee shops andother external unsecured hotspots.

The unified agent application 600 provides authenticated and encryptedtunnels from road warrior devices 604 and, in some use cases, it evenneeds to be enforceable so that end users cannot disable the unifiedagent application 600. The VPN, which is the remote access service, alsoneeds to be authenticated and encrypted tunnel from road warrior devices604. Both of these solutions also need to provide feedback to the enduser in the event that access was blocked due to security or compliancereasons. The following describes the architecture and design of theunified agent application 600 including an endpoint client architecture,backend changes, auto update and integration with the security cloud608.

The unified agent application 600 includes logical components includingview components 702, business processes and services 704, data 706, andcross-cutting functions 708. The view components 702 include UserInterface (UI) components 710 and UI process components 712. Thebusiness processes and services 704 include a tray user process 714, ahelper user process 716, a tunnel system service 718, a posture systemservice 720, and an update system service 722. The data 706 includesencrypted data 724, configuration data 726, and logs 728. Thecross-cutting functions 708 are across the view components 702, thebusiness processes and services 704, and the data 706 and includesecurity 730, logging 732, and statistics 734.

The unified agent application 600 has a use goal of simplifiedprovisioning of the proxy (for security through the security cloud 608to the Internet 504) and the VPN (for access through the security cloud608 to the enterprise private resources 612). That is, the unified agentapplication 600 allows the use of the distributed security system 100,the cloud system 500, the distributed security cloud 552, the securitycloud 608, etc. as a proxy for Internet-bound communications. Theunified agent application 600 further allows the use of the distributedsecurity system 100, the cloud system 500, the distributed securitycloud 552, the security cloud 608, etc. as a tunnel for Intranet-boundcommunications to the enterprise private resources 412. With the unifiedagent application 600 setting up a local network at the device 604, theunified agent application 600 can manage communications between theInternet and the Intranet, i.e., two of the main categories of cloudservices—proxy to the Internet and tunnel to the Intranet. The unifiedagent application 600 further has objectives of simplified userenrollment in the proxy and tunnels.

In an exemplary embodiment, the unified agent application 600 is anative application. The common functionality is abstracted out and madeinto common libraries based on C or C++ so that it can be reused acrossdifferent platforms (e.g., iOS, Android, etc.). Example functionality:Traffic forwarding tunnels, local proxy, authentication backend,logging, statistics, etc. The UI components 710 and UI processcomponents 712 can be platform dependent. Also, the unified agentapplication 600 is designed and implementable such that other thirdparty VPN applications if configured by the enterprise, can be usedconcurrently.

The app portal 632 enables installation of the unified agent application600 on the device 604. For example, an admin may be able to push andinstall the unified agent application 600 to the device 604 usingremote-push mechanisms like GPO, MDMs, etc. Additionally, the user candownload the unified agent application 600 if they have access toinstallation file and install on their own. The unified agentapplication 600 supports automatic updates without impacting the user'sInternet experience. If a problem is encountered, then it should rollback to previously successful state or fail open. The unified agentapplication 600 can have a security check to ensure that it is nottampered and updated from a right source with a hash match with a sourcehash when upgrading.

The user is able to log into the unified agent application 600 such aswith a User ID and password, as illustrated in FIG. 11. Once the usersends their User ID through the unified agent application 600 to theagent manager cloud 606, the security cloud 608, and/or the app portal632, the app portal 632 can determine the company's authenticationmechanism, such as through a lookup in the enterprise asset management614, and validate password through the enterprise CA 618.

Through the unified agent application 600, a user can be authenticatedto the proxy or the VPN through the security cloud 608. Forauthentication of the user to the proxy, using SAML, the user is able tolog into the unified agent application 600 by using their user ID andtransparent SAML authentication thereafter, including SAML certificate.The app portal 632 shall determine that an organization is using SAMLfor authentication through the enterprise CA 618 and redirect to theenterprise SAML IDP 616 to get SAML assertion and use it to authenticatethe user.

For authentication of the user to the tunnel, using SAML, the user isable to log into the unified agent application 600 by just using theiruser ID and based on the user ID, the unified agent application 600shall redirect the user for authentication to enterprise SAML IDP 616and SAML assertion shall be sent. The VPN service shall validate SAMLassertion; if the assertion is valid, then the unified agent application600 shall collect hardware parameters like device serial number, modelnumber, etc. and create CSR. The CSR shall be signed by the enterpriseCA 618 and the certificate shall be pushed to the unified agentapplication 600. The unified agent application 600 shall install thecertificate to KMS/keychain and save assertion.

After the user has been successfully authenticated, the user shall beenrolled in the proxy service and user's traffic forwarding profileshall be downloaded from unified agent application 600 including SecureSockets Layer (SSL) certificates and exceptions. The unified agentapplication 600 shall indicate that user is connected to security cloud608, and app statistics shall be populated.

After the user has successfully authenticated (including transparentauthentication), the user shall be enrolled with a VPN service and theVPN broker info shall be downloaded by the unified agent application 600and the VPN tunnel shall be established. The unified agent application600 can support captive portal detection to fail open when users arebehind a captive portal to allow connection to captive portal.

The unified agent application 600 can forward enterprise internaltraffic from the device 604 to the VPN. The unified agent application600 can recognize when a user goes to an internal app that isprovisioned with the VPN service. The unified agent application 600shall auto enable a tunnel to the VPN service when the user triesconnecting to an internal app. The proxy service can always be enforced,and the user is not able to remove it by switching off tunnel orremoving the unified agent application 600. Without the proxy solutionenforced, the user is not able to access the Internet and would beprompted to restart the web security service, via the unified agentapplication 600.

The VPN is an on-demand service; unlike the proxy service that shall beenforceable by default, so the user can enable/disable the VPN at willwithout any password requirements. Once the user logs into the VPNservice using a ‘Connect,’ the same button shall be labeled ‘Disconnect’and user shall be able to disconnect the VPN service with a singleclick. Every time user disconnects with VPN service. The VPN service canbe auto-disabled if the user puts their system to sleep mode or there isinactivity (no packets exchanged) after x minutes (x shall beconfigurable in the VPN settings).

The admin can turn off the proxy service with a single client from anadmin UI for a user, all users, or some subset of users. This does notremove the unified agent application 600 from the device 604. A user maybe able to disable the proxy service, provided they have the authorityand credentials. The unified agent application 600 can provide servicerelated notifications to the user. For example, the unified agentapplication 600 can provide notifications such as push alerts or thelike as well as contain a notification area for a single place to showall notifications that are generated by the proxy service and the VPNservice. This shall also include app notifications includingconfiguration updates, agent updates, etc. The user shall be able toclear notifications as well filter notifications from this screen. Thisshall include a filter for VPN/Proxy, blocked, cautioned, quarantineactions.

§ 7.4 Unified Agent Application—Admin Workflow

Referring to FIGS. 12 and 13, in an exemplary embodiment, screen shotsillustrate an admin dashboard (FIG. 12) and a network evaluationconfiguration (FIG. 13) for the unified agent application 600. Anenterprise administrator (admin) can configure the unified agentapplication 600 for associated users. Configurable parameters generallyinclude the Acceptable Use Policy (AUP), automatic updates, enforcementparameters (e.g. logout password to allow the user to log out of theunified agent application 600, uninstall password to allow the user touninstall the unified agent application 600, etc.). For the proxyservice, the configurable parameters can include Proxy Auto-Config (PAC)per user, group, etc. Also, the proxy service can be enabled for allusers, for subsets of users, and/or for individual users. For the VPNservice, the configurable parameters can include certificates, IDPservers, ports and protocols, and the like.

The admin dashboard provides a centralized view for all the users of theunified agent application 600, including deployed licenses, device 604type and Operating System (OS), device policy status, platform type,etc. The network evaluation configuration allows the admin to add atrusted network profile and perform other configurable parameters withthe proxy service and the VPN service.

§ 7.5 Unified Agent Application—User Workflow

Again, the unified agent application 600 is executed on the device 604.For authentication, the user enters a User ID in the unified agentapplication 600, such as userid@domain. Subsequently, the unified agentapplication 600 is configured to discover the services enabled—proxyservice and VPN services based on userid@domain. The user authenticateswith the presented services, i.e., proxy service, VPN services, andcombinations thereof. The unified agent application 600 is autoprovisioned for the authenticated service by downloading the servicespecific configuration. The unified agent application 600 performs thefollowing during VPN enrollment—get the User/Device certificate signedby an Enterprise Intermediate Certificate. This Intermediate Certificatewill be same which will be used for signing Assistants. The unifiedagent application 600 also will pin hardware signatures/fingerprints tothe Certificate and user, e.g., Storage Serial ID (Hard Drive SerialID), CPU ID, Mother Board Serial ID, BIOS serial number, etc.

§ 7.6 Unified Agent Application—Authentication and Enrollment Protocol

Referring to FIG. 14, in an exemplary embodiment, a flowchartillustrates a proxy authentication method 750 to the security cloud 608.For authentication in the proxy service, conventionally, devices 604 canuse proxy authentication to register to the security cloud 608. This isnot truly reliable as it depends on location/location-authenticationpolicy/VPN and other such factors to work correctly. To simplify thisflow, the following new flow can be used with the unified agentapplication 600 for the method 750. First, the mobile client device 604initiates an HTTPS request to a CA (e.g., the enterprise CA 618) (step752). For example, this can be as follows:

login.zscaler.net/clstart?version=1&_domain=nestle.com&redrurl=<url-encoded-url-with-schema>If the domain is invalid or if the redrurl is missing, CA will reset theconnection.

Above end-point begins the client auth flow (step 754). The provideddomain is the company that requires the auth. The CA looks up the domainto find the company and their auth mechanism. If the company uses hostedor Active Directory (AD)/Lightweight Directory Access Protocol (LDAP)authentication [SAML auth flow starts at step 760], the response will bea login form with input fields for [username] & [password] (step 756).The form is submitted via POST to the CA at a below end-point:

https://login.zscaler.net/clicred. The HTTP content may look like below

POST/clicred

Host: login.zscaler.netContent-Length: xyzusername=xyz@nestle.com&password=123456&redrurl=<url-encoded-posturl-with-schema>

Next, the CA performs user/password validation and responds with themessage explained in step 764 (step 758). If the company uses SAML,response to the request in step 752 will be the SAMLRequest form. TheSAMLRequest form will auto-submit to the IDP. Once auth completes, theCA gets control back with the identity of the user. Once SAMLResponsecomes back, send the response as a 307 redirect to redrurl with a belowformat

Location: zsa://auth[?token=encrypted-cookie& . . . ] to be appended.307 query paramstoken=(on success)ecode=(on error)emsg=(on error)On error, send the same redrurl with below formatzsa://auth? ecode=<code>&emsg=<message>

Referring to FIG. 15, in an exemplary embodiment, a flowchartillustrates a VPN authentication method 780 to the security cloud 608.The client (device 604) issues a GET web request to the VPNauthentication server with domain name as the query parameter (step782), such as:

GET //<auth-server>?domain=mockcompany.com

The server identifies the IDP for the given domain and responds with aHypertext Markup Language (HTML) page containing a SAML Request (step784). The client will redirect to the IDP with the SAML Request (step786). The IDP will challenge the client for credentials which can be ofthe form of username/password or client identity certificate (step 788).On successful authentication, IDP will generate an SAMLResponse for theVPN authentication server (step 790). The client will record theSAMLAssertion for future tunnel negotiation. In the case of error, theserver will resend the challenge to the user (step 792).

Referring to FIG. 16, in an exemplary embodiment, a flowchartillustrates a device enrollment method 800 for the client device 604 andthe unified agent application 600. Post successful authentication withall services, in this case, the proxy services and the VPN services, theclient sends an enrollment request to mobile admin (Cloud AdministrativeServer CAS) (step 802). The request contains device fingerprint andauthentication context for each service to identify the user (step 804).For example, the security cloud 608 can use cookies, and the VPN can useSAMLAssertion for the authentication context. The mobile admin (agentmanagement cloud 606) performs inventory lookup with device fingerprintsat the MDM server to authorize the user and the device 604 (step 806).On successful authorization, the mobile admin server enrolls the user tocloud services with their authentication contexts (step 808). Each cloudservice responds with specific access controls and protocol informationthat the client receives from mobile admin and uses for local networksetup (step 810).

§ 7.7 Unified Agent Application—Traffic Interception and Splitting

Again, in order to protect Internet-bound traffic and simultaneouslyaccess Enterprise specific Intranet traffic, the device 604 needs toconnect through multiple applications. Again, it is not straightforwardfor users to configure these applications in different networks anddifferent VPN and proxy solutions arise compatibility issues whenoperating simultaneously. The unified agent application 600 is designedto solve all these issues. The unified agent application 600 handlesboth proxy (Internet-bound) traffic, and Enterprise Intranet boundtraffic. The unified agent application 600 provides secure access toOrganizational internal resources when the user is outside of theenterprise network. For Internet-bound traffic, it will forward trafficto the processing node 110 or the cloud node 502, and for Intranet boundtraffic, it will forward traffic to a VPN (Broker) or direct if the useris inside the organization network.

The unified agent application 600 is configured to intercept alltraffic, specifically to intercept all Transmission Control Protocol(TCP) traffic and DNS traffic before it goes out through the externalnetwork interface in the device 604. The unified agent application 600can intercept other types of traffic as well, such as User DatagramProtocol (UDP). The unified agent application 600 is configured to splittraffic at the device 604, i.e., based on a local network configured atthe device 604. Split traffic can be as follows: if the VPNservice isconfigured by admin, traffic destined to internal hostnames(configured/provided by company admin) will go to the VPN (broker), ifthe proxy service is configured by admin, rest of 80/443 traffic will goto the security cloud 608 or will go direct based on PAC file configuredby admin, and the remaining traffic will go directly. The unified agentapplication 600 is configured to send VPN traffic direct for trustednetworks (organization's internal network). The unified agentapplication 600 can also coexist with other VPN clients, i.e. it doesnot intercept the traffic targeted for those interfaces by specificroutes.

Thus, the unified agent application 600 is configured to intercept alltraffic at the IP layer for the device 603 or other VPN client's defaultroute. Then, the unified agent application 600 is configured to splittraffic to the VPN [for darknet hosted applications], Proxy [forinternet-bound cloud services] or Direct [for uninspected traffic] atboth the IP or Transport layer.

Referring to FIG. 17, in an exemplary embodiment, a flowchartillustrates a traffic interception method 820 implemented through theunified agent application 600. The unified agent application 600registers and sets up a new Network Adapter (TUN interface) on thedevice (step 822). The unified agent application 600 overrides thedevice's network default route by configuring the default route ofhigher priority for the TUN interface (step 824). The unified agentapplication 600 sets specific route (exact match) for all DNS serversconfigured on the device 604 with the highest priority (step 826). Theunified agent application 600 will not override other specific routes ofexternal adapter or other VPN clients (step 828). The unified agentapplication 600 will open one UDP listening socket (for all UDP traffic)and two TCP listening sockets (one for VPN traffic and the other forrest of traffic) (step 830).

For each client socket coming to the UDP listening socket port, theunified agent application 600 includes accepting the client socket, ifit is a DNS (port 53), a query is performed; else a UDP socket iscreated (step 832). The query includes if hostname matches oneconfigured by admin for the VPN, the unified agent application 600 willcreate a local DNS response packet with address a.b.c.d, else it willcreate a UPD socket, bind it to external Interface and send the DNSpacket to the original DNS server, and the response is written back tothe client socket. For creating the UDP socket, it is bound to anexternal interface, a request packet is sent to the original destinationserver, and a response is written back to the client socket.

For each IP packet coming to the TUN interface, packet processing isperformed (step 834). Here, if the packet's source port is equal to anyof the unified agent application 600 listening socket's port then, getvalue corresponding to the packet destination port from the mappingtable and replace packet source port with this value, else add akey-value entry <source port, destination port> to a mapping table andreplace packet's destination port as per the following rules. If theprotocol is UDP, replace with UDP listening socket port, if the protocolis TCP and destination address is a.b.c.d, replace with the VPNlistening socket port, else replace with the second TCP listening socketport. Next, swap the source and destination IP addresses, compute IP andTCP/UDP checksums and overwrite original checksums in the packet, andwrite modified packet to the external interface.

For example, assume x.x.x.x is the IP address of the TUN interface andzz is the local listening socket port, the following illustrates anexample of packet processing:

Original Packet Modified Packet Request packet from client app: Src:y.y.y.y:xx Dest: .x.x.xx:zz Src: x.x.x.x:xx Dest: y.y.y.y:yy Entry addedto mapping table: <xx,yy> Response packet from listening socket: Entryfetched from mapping Src: x.x.x.x:zz Dest: y.y.y.y:xx table for key xxis yy Src: y.y.y.y:yy Dest: x.x.x.x:xx

Next, for each client socket coming to the VPN listening socket port,processing is performed (step 836). The processing includes acceptingthe client socket, if the connection to the VPN is not there, create asocket for the VPN server, bind it to the external interface and connectand authenticate to the VPN; read request data from the socket and writeit to the VPN server socket according to VPN protocol, and read responsedata from VPN socket and write it back to client socket.

For each client socket coming to the second TCP listening socket port,processing is performed (step 838). The processing includes acceptingthe client socket, if original destination port is 80/443, if thehost/IP/URL is bypassed in a PAC file, then create new socket direct todestination server/port, else create new socket (or reuse existingsocket) to the security cloud 609 and send connect request for thedestination IP and port, else create new socket direct to destinationserver/port. Once the socket in connected, write request data on it, andwhen a response is available, write it back to the client socket.

Referring to FIG. 18, in an exemplary embodiment, a flow diagramillustrates traffic interception and splitting 850 using the unifiedagent application 600. Again, the unified agent application 600 createsand operates a tunnel (TUN) interface 852 on the device 604. The device604 includes one or more client applications 854, which can be anyprogram or service executable on the device 604 which requires access tothe network interface on the device 604. Traffic for the default routefrom the client applications 854 is sent to the TUN interface 852, buttraffic for specific routes can be sent to other interfaces 856,separate from the TUN interface, for direct connectivity to the Internet504, such as via VPN services or direct.

The TUN interface 852 splits 858 all traffic. TCP traffic for internaldomains is sent to a VPN/broker server 860, TCP port 80/443 traffic issent to the security cloud 608 for a proxy such as to the processingnode 110 or the cloud node 502. Finally, other traffic can be sentdirectly to the Internet 504. In this manner, the TUN interface 852operates a local network at the device 604.

Referring to FIG. 19, in an exemplary embodiment, a flow diagramillustrates the exemplary functionality of client applications 864, theTUN interface 852, sockets 862, 864, and the VPN/broker server 860 forthe interception and splitting 850 using the unified agent application600. Specifically, FIG. 19 illustrates activity between the clientapplications 864, the TUN interface 852, a UDP listening socket 862, aVPN listening socket 864, and the VPN/broker server 860. First, theclient application 854 sends a DNS query for an internal domain (step902). The TUN interface 852 receives the IP packet corresponding to theDNS request and changes the packet's destination to the UDP listeningsocket 862 and writes the packet back (step 904). The UDP listeningsocket 862 receives the UDP socket connection, accepts the socket,creates and writes a local DNS response packet with A.B.C.D address(step 906). The DNS response is sent from the UDP listening socket 862to the TUN interface 852 (step 908) and modified and sent back to theclient application 854 (step 910).

Next, the client application 854 opens a TCP socket to A.B.C.D:XX andwrites request data (step 912). The TUN interface 852 receives the IPpacket corresponding to the TCP socket and changes the packet'sdestination address to the VPN listening socket 864 and writes thepacket back (step 914). The VPN listening socket 864 receives the TCPsocket connection, accepts the socket and read request data, and createsthe socket through an external interface to connect and authenticate tothe VPN server 860 and write TCP request data (step 916). The VPN server860 sends TCP response data (step 918), the VPN listening socket 864writes a response back to the client socket (step 920), and the TUNinterface 852 modifies the packet and sends TCP response data (step922).

Referring to FIG. 20, in an exemplary embodiment, a flow diagramillustrates tunnel forwarding rules 940 by the unified agent application600. A periodic health monitor function 942 operates, based on aperiodic timer 944, to check a PAC ping and a gateway connect ping toprovide a state to a bypass fail/open module 946. A network state changefunction 948 is configured to detect a network change event 950 such asDNS server address, DNS search domains, on-net host DNS lookups, etc.,and to provide a state to the bypass fail/open module 946. The bypassfail/open module 946 creates an active tunnel 952 or disabled tunnel 954based on the states.

§ 8.0 Multidimensional Risk Profiling for Network Access Control

Referring to FIG. 21, in an exemplary embodiment, a flowchartillustrates a multidimensional risk profiling process 1000 for NAC via acloud based security system 100, 500, 550 and the unified agentapplication 600. Again, the multidimensional risk profiling process 1000is a dynamic risk profiling mechanism for mobile devices from variousdimensions which is then used to evaluate network access control by thecloud based security system. In this manner, the multidimensional riskprofiling process 1000 provides a context-aware, user adaptive andintelligent way to control network access.

The multidimensional risk profiling process 1000 includes authenticationwhere a mobile device is authenticated through the cloud based securitysystem (step 1002). For example, when a user requests network access,the client application on the mobile device can perform authenticationwith the IDP, and after successful authentication, the user is grantedaccess to the network through a network tunnel to the cloud basedsecurity system. The mobile device is coupled to the cloud basedsecurity system via a client application, i.e., the unified agentapplication 600. The network access and authentication can be via theclient application.

The multidimensional risk profiling process 1000 includes the mobiledevice coupled to the cloud based security system through a tunnel viathe client application (step 1004). That is, the user is granted accessto the network through a network tunnel to the cloud based securitysystem. The multidimensional risk profiling process 1000 includesposture acquisition where the client application collects data (step1006). Specifically, the client application can collect deviceinformation and security telemetry and communicates it to the cloudbased security system. The client application listens for securitycritical events such as Operating System (OS) upgrades, abruptgeolocation changes, device information deviation, and changes in theinstalled application list and updates the cloud based security system.The cloud based security system evaluates the changes and computes a newrisk index for the device.

The multidimensional risk profiling process 1000 includes posturefingerprinting where the cloud based security system creates a mobiledevice fingerprint (step 1008). Specifically, the cloud based securitysystem creates a device fingerprint and a risk index for the mobiledevice based on the nature of applications installed on the system,operating system vulnerabilities, anti-virus status, patch level, deviceconfiguration, and the like. The multidimensional risk profiling process1000 includes threat data management where the cloud based securitysystem collects information related to threats (step 1010). The cloudbased security system has a data enriching feed mechanism which collectsinformation on all available threats at regular intervals. Based on thethreat information, the cloud based security system performs a threatanalysis of the mobile device at regular intervals and updates theassociated risk index.

The multidimensional risk profiling process 1000 includesmultidimensional risk appraisal where access to network resources isthrough the cloud based security system as a function of risk (step1012). That is, the access to any resource on the network is a functionof the risk of temporal credentials that are generated by the cloudbased security system for that particular resource at that time. Thetemporal credentials embody risk information of the user requesting theaccess, the mobile device and the application which are being used toaccess the resource, and the nature of resource itself. For example, abanking website has higher associated risk and must be denied from ahigh-risk application.

The multidimensional risk profiling process 1000 includes adaptiveaccess control where access to sensitive resources is limited based onrisk (step 1014). For example, for access to sensitive resources such ascorporate applications, a high-risk user will be challenged with amulti-factor authentication scheme as configured by the enterprise.Also, based on the enterprise policy, the network can be quarantined tolimit access to certain applications only. The multidimensional riskprofiling process 1000 includes dynamic risk enrichment where riskscores for the mobile devices are updated based on activity (step 1016).Based on the network usage, the risk score of the user is updated witheach network access. For example, access to malware or phishing sites,increases the risk index of the user. The client application listens forsecurity critical events such as OS upgrades, abrupt geolocationchanges, device information deviation, and changes in the installedapplication list and updates the cloud security system. The cloud basedsecurity system evaluates the changes and computes a new updated riskindex for the mobile device.

The multidimensional risk profiling process 1000 includesmultidimensional risk correlation where the risk scores are updated forthe mobile device based on multiple dimensions. A cloud based approachallows correlation of risk from multiple dimensions. For example, if aknown family of malware is correlated with an application, then the riskindex of the application increases and thereby any user accessing theInternet from the same application will face a higher risk penalty.Similarly, if multiple malware requests are getting originated from thesame geolocation, then the geolocation IP subnet may be flagged formalicious activity, and any user accessing the network from the samesubnet or trying to access the same subnet may face stringent networkaccess control.

The multidimensional risk profiling process 1000 surmounts thechallenges imposed by on-premise NAC systems. Using the mobile devicesin the enterprise with the cloud based security system as disclosedherein creates a win-win situation for employees and the corporates.Using the cloud based security system that employs multidimensional riskprofiling of mobile devices, intelligent access control decisions can beachieved that minimizes the security risk and maximizes the userproductivity. The cloud based approach to assess risk eliminates theneed for updating NAC servers with emerging threats information. Basedon user risk, access to sensitive web resources (such as bankingwebsites) or internal corporate resources can be denied or supported bymulti-factor risk-based authentication models. Granular networkquarantine restrictions can be achieved based on the risk level of theuser and the enterprise policy. With a cloud based approach to networkaccess control, risk can be correlated universally from multipleperspectives that further accounts for better security. For example, ifan otherwise benign user is trying to access an application which wasrecently accessed by a family of malware, the access can be immediatelydenied/quarantined.

§ 8.1 Risk Appraisal and Enrichment

Access to any network resource is a function of the Risk associated withthe request. Let say a User “x” uses Application “a” on Device “d” toaccess a network resource “r” at time t. Temporal Risk is denoted byR(t) for tuple <x,a,d,r,t>.

${R(t)} = \frac{{w_{a}{U_{x}(t)}} + {w_{b}{A(a)}} + {w_{c}{D(d)}} + {w_{d}{{NR}(r)}} + {w_{e}{E(t)}}}{w_{a} + w_{b} + w_{c} + w_{d} + w_{e}}$

where U_(x) is the risk profile of user “x” till time “t”, A is the riskassociated with application “a”, D is the risk associated with deviceposture “d”, NR is the risk associated with accessing resource “r”, Edefines the environmental factors contributing to risk at time “t”. Thiscan include aspects like geolocation, user intention, global threatconditions. w_(x) are the weights associated with the risk and can beconfigured as per the enterprise policy. For example, an enterprise thatweighs application vulnerabilities more than the device vulnerabilitywill have w_(b)>w_(c). Note that all Risk functions have a range [−1, 1]where 1 denotes 100% risk, 0 denotes a 50% risk and −1 denotes no risk.

R(t)ϵ[−1,1].

U_(x) captures the risk profile of the user which changes with time andis directly proportional to the network access history, with presentaccess weighing more than the past access:

$\mspace{76mu} {{U_{x}(t)} \propto {\sum\limits_{a = 1}^{t}\; {\left( {t - a + 1} \right)\mspace{14mu} {R\left( {t - a} \right)}}}}$     At  t = 0, U_(x)(0) = −1      At  t = 1, U_(x)(1) = R(0)$\mspace{76mu} {{{{At}\mspace{14mu} t} = 2},{{U_{x}(2)} = {{{\frac{{2.{R(1)}} + {1.{R(0)}}}{2 + 1}\mspace{76mu}.\mspace{76mu}.\mspace{76mu}.\mspace{76mu} {At}}\mspace{14mu} t} = n}},{{U_{x}(n)} = \frac{{n.{R\left( {n - 1} \right)}} + {\left( {n - 1} \right)\mspace{14mu} {R\left( {n - 2} \right)}} + {\left( {n - 2} \right){R\left( {n - 3} \right)}} + \ldots \; + {R(0)}}{n + \left( {n - 1} \right) + \left( {n - 2} \right) + \left( {n - 3} \right) + \ldots \; + 1}}}$

This equation embodies the risk of the user at a current time based onthe previous network access history. Recent access is weighed more thanpast access that is linearly discounted, i.e., the user is penalizedbased on how recent the user had a high temporal risk while accessing anetwork resource.

§ 8.2 Adaptive Access Control

Based on the temporal risk and enterprise policy, access to networkresources can be controlled. Once a risk score is calculated for aparticular access attempt, it is weighed against the relative level ofrisk tolerance assigned to the resource asset, for example:

if −1≤R(t)<0, access to network resource will be unconditionally ALLOWEDif 0≤R(t)<δ, access to network resource will be QUARANTINED where δ isthe enterprise specific risk tolerance. Further the user can beCAUTIONED to take remediation steps.if δ≤R(t)≤1, access to network resource will be DENIED

While this rule set applies for individual network resources, it canfurther be extended to quarantine or deny, entire or partial networkaccess to a group of applications or the whole Internet. The evaluativecriteria can be extended as: if (R(t)=∫_(t) ₀ ^(t)R(t)dt)>ϕ then denynetwork access; where t−t₀ is the duration of cumulative risk evaluationand ϕ is the enterprise specific risk-limit beyond which all networkaccess is denied. It essentially captures the number of penalties that auser is allowed beyond which the user has to lose access to network orget a quarantined version of it.

§ 8.3 Exemplary Implementation of Multidimensional Risk Profiling

In an exemplary implementation, the multidimensional risk profilingprocess 1000 can be implemented through various modules such asauthentication, tunneling, posture acquisition, posture fingerprinting,threat data management, multidimensional risk appraisal, adaptive accesscontrol, dynamic risk enrichment, and multidimensional risk correlation.

§ 8.4 Authentication

The unified agent application 600 can perform authentication with anenterprise IDP as configured and network access can be disallowed priorto authentication. In an exemplary embodiment, the mobile clients canuse proxy authentication to register to the cloud based security system.This is not truly reliable as it depends on location/location-authpolicy/VPN and other such factors to work correctly. To simplify thisflow, the following new flow is proposed.

(1) The mobile client, e.g., the unified agent application 600,initiates an HTTPS request to CA as below:

login.zscaler.net/clstart?version=1&domain=nestle.com&redrurl=<url-encoded-url-with-schema>The query params are version=, domain=, redrurl=, GET/clstart?version=1&domain=nestle.com&redrurl=<url-encoded-posturl-with-schema>, the host islogin.zscaler.net. On errors, domain is invalid [error in 307] or theredrurl is missing [reset connection].

(2) The above end-point begins the client authentication flow. Theprovided domain is the company that requires the authentication. The CAlooks up the domain to find the company and their authenticationmechanism. (3) If the company uses hosted OR ad/LDAP AUTH, [SAML AUTHflow starts at (5)]. The response will be a login form with input fieldsfor [username] & [password]. The form is submitted via POST to the CA atbelow end-point.

login.zscaler.net/clicred. The HTTP content may look like

POST/clicred

Host: login.zscaler.netContent-Length: xyzusername=xyz@nestle.com&password=123456&redrurl=<url-encoded-posturl-with-schema>

(4) CA performs user/password validation and responds with the messagein (7). (5) If the company uses SAML, the response to the request (1)will be the SAMLRequest form. The SAMLRequest form will auto-submit tothe IDP. Once authentication completes, the CA gets control back withthe identity of the user. (6) Once the SAMLResponse comes back, theresponse in the message (7) is sent. (7) After authentication, a 307redirect is sent to REDURL with a below format

Location: zsa://auth[?token=encrypted-cookie& . . . ] to be appended.307 query params-token=(on success), ecode=(on error), emsg=(on error).On error, the same REDURL is sent with below formatzsa://auth? ecode=<code>&emsg=<message>

For tunnel authentication, (1) the client issues a GET web request tothe tunnel authentication server with the domain name as the queryparameter:

GET https://<auth-server>?domain=mockcompany.com(2) the server identifies the IDP for the given domain and responds withan HTML page containing a SAML Request. (3) the client will redirect tothe IDP with the SAML Request. (4) the IDP will challenge the client forcredentials which can be of the form of username/password or clientidentity certificate. (5) on successful authentication, the IDP willgenerate an SAMLResponse for the tunnel authentication server. Theclient will record the SAMLAssertion for future tunnel negotiation. (6)In the case of error, the server will resend the challenge to the user.

§ 8.5 Tunneling

The unified agent application 600 can tunnel all network traffic to thecloud based security system. The objectives of tunneling are (i)intercept all traffic at IP layer for system's or other VPN client'sdefault route, and (ii) split traffic to the tunnel [for darknet hostedapplications], Proxy [for Internet-bound cloud services] or Direct [foruninspected traffic] at both IP or Transport layer.

§ 8.6 Posture Acquisition

The unified agent application 600 collects device information atrelevant time intervals. This information can include, withoutlimitation: device hardware parameters, Applications Reputation,Applications Change List, OS Patches. Application versions, and thelike. For example, the following posture is collected from the devicewherever applicable and allowed:

Processor Signature->

-   -   CPUID

Using IOCTL:

Battery->

-   -   BatteryManufactureName    -   Battery SerialNumber    -   BatteryUniqueID

Storage->

-   -   VendorId    -   ProductId    -   SerialNumber    -   BusType    -   Storage Cache->        -   Version        -   . . .

Network Interface Card->

-   -   Mac Address

§ 8.7 Posture Fingerprinting

The unified agent application 600 collects all the posture informationand can create an SHA-256 HASH of the information, and assigns a uniquedevice-id in a UUID format to the client. This device-ID is used totrack the device in all the network access requests that the clientgenerates.

§ 8.8 Threat Data Management

The cloud based security system can be coupled to multiple threatdatabases that provide updated information on (1) Application RiskReputation across different Application Versions and Operating Systems;(2) Operating System Vulnerabilities; (3) Web Resource Risk Potentialbased on phishing content, malicious content, advanced security riskssuch as Cross-Site Scripting (XSS), cookie stealing, DLP, and the like;(4) Command and Control (C&C) Botnet servers; and the like.

§ 8.9 Multidimensional Risk Appraisal

The cloud based security system can perform risk appraisal for everyrequest to any network resource. Risk evaluation is a function of devicerisk, application risk, resource risk, user risk, and environment risk.The device risk embodies risk involved in accessing a resource from avulnerable device such as based on OS vulnerabilities, a number ofhigh-risk applications installed on the device, etc. The applicationrisk embodies risk involved in using a specific application to access aspecific resource. For example, using an unsafe browser to accessintranet resources, can result in a data breach. The resource riskembodies potential of the network resource to cause damage. The userrisk is based on the user's network behavior to determine the riskassociated with giving access to the user. The environment risk is basedon geolocation IP and other environmental factors.

§ 8.10 Adaptive Policy and Access Control

This cloud based approach allows extending role based access control torisk adaptable policy and access control, where access to a resource onthe network is not only a function of the user role but is alsodependent on how risky it is to give access to the user. This makepolicy and access control: context sensitive and adaptable to user risk.

§ 8.11 Dynamic Risk Enrichment

The risk profile of the user is based on the user browsing pattern whichmakes the risk profile dynamic. This allows giving access to users whoare benign irrespective of whether they are carrying a known or unknowndevice, catering to the Bring your own Device (BYOD) model of operation.

§ 8.12 Multidimensional Risk Correlation

Risk can be correlated in the cloud based security system from multipledimensions of the device, application, resource, user risk, and theenvironment. Millions of data points can be correlated to update riskprofiles of users. For instance, if a malicious user with high-riskindex uses a set of applications that are statistically similar toanother set of applications on another user's device, the risk profileof the latter user can then be updated accordingly. Such statisticalsimilarities between applications, devices, user browsing patterns,geographic proximity, can be leveraged to protect enterprises againstmalicious encroachments and violation of enterprise access controlpolicies.

It will be appreciated that some exemplary embodiments described hereinmay include one or more generic or specialized processors (“one or moreprocessors”) such as microprocessors; Central Processing Units (CPUs);Digital Signal Processors (DSPs): customized processors such as NetworkProcessors (NPs) or Network Processing Units (NPUs), Graphics ProcessingUnits (GPUs), or the like; Field Programmable Gate Arrays (FPGAs); andthe like along with unique stored program instructions (including bothsoftware and firmware) for control thereof to implement, in conjunctionwith certain non-processor circuits, some, most, or all of the functionsof the methods and/or systems described herein. Alternatively, some orall functions may be implemented by a state machine that has no storedprogram instructions, or in one or more Application Specific IntegratedCircuits (ASICs), in which each function or some combinations of certainof the functions are implemented as custom logic or circuitry. Ofcourse, a combination of the aforementioned approaches may be used. Forsome of the exemplary embodiments described herein, a correspondingdevice such as hardware, software, firmware, and a combination thereofcan be referred to as “circuitry configured or adapted to,” “logicconfigured or adapted to,” etc. perform a set of operations, steps,methods, processes, algorithms, functions, techniques, etc. as describedherein for the various exemplary embodiments.

Moreover, some exemplary embodiments may include a non-transitorycomputer-readable storage medium having computer readable code storedthereon for programming a computer, server, appliance, device,processor, circuit, etc. each of which may include a processor toperform functions as described and claimed herein. Examples of suchcomputer-readable storage mediums include, but are not limited to, ahard disk, an optical storage device, a magnetic storage device, a ROM(Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM(Erasable Programmable Read Only Memory), an EEPROM (ElectricallyErasable Programmable Read Only Memory), Flash memory, and the like.When stored in the non-transitory computer readable medium, software caninclude instructions executable by a processor or device (e.g., any typeof programmable circuitry or logic) that, in response to such execution,cause a processor or the device to perform a set of operations, steps,methods, processes, algorithms, functions, techniques, etc. as describedherein for the various exemplary embodiments.

Although the present disclosure has been illustrated and describedherein with reference to preferred embodiments and specific examplesthereof, it will be readily apparent to those of ordinary skill in theart that other embodiments and examples may perform similar functionsand/or achieve like results. All such equivalent embodiments andexamples are within the spirit and scope of the present disclosure, arecontemplated thereby, and are intended to be covered by the followingclaims.

What is claimed is:
 1. A server configured to profile a mobile devicefor a cloud-based system, the server comprising: a network interface, adata store, and a processor communicatively coupled to one another; andmemory storing computer executable instructions, and in response toexecution by the processor, the computer-executable instructions causethe processor to based on communication to a client application on themobile device, cause the client application to collect data associatedwith the mobile device; receive the collected data; and determine adevice fingerprint and a risk index for the mobile device based on thecollected data, wherein the device fingerprint is utilized to uniquelyidentify the mobile device and the risk index is utilized to manage themobile device.
 2. The server of claim 1, wherein the collected dataincludes any of device information, security telemetry, operating systemupgrades, geolocation changes, application changes, anti-virus status,device configuration, and combinations thereof.
 3. The server of claim1, wherein the cloud-based system utilizes the device fingerprint toauthorize a user and for tracking the user in all network accessattempts.
 4. The server of claim 1, wherein the device fingerprint is acombination of posture information from the collected data and isrepresent as a hash of the posture information.
 5. The server of claim1, wherein the risk index is utilized for access to or through thecloud-based system.
 6. The server of claim 1, wherein the risk index isbased on a combination of user browsing pattern, device risk,application risk, resource risk, user risk, and environment risk.
 7. Theserver of claim 1, wherein the risk index is continually updated.
 8. Theserver of claim 1, wherein the memory storing computer executableinstructions, and in response to execution by the processor, thecomputer-executable instructions cause the processor to one of allow,quarantine, or deny a user request to resources in or through thecloud-based system based on the risk index.
 9. A mobile devicecomprising: a network interface, a data store, and a processorcommunicatively coupled to one another; and memory storing computerexecutable instructions, and in response to execution by the processor,the computer-executable instructions cause the processor to execute aclient application that communicates to a cloud-based system; collectdata associated with the mobile device via the client application; andtransmit the collected data to the cloud-based system, for adetermination of a device fingerprint and a risk index for the mobiledevice based on the collected data, wherein the device fingerprint isutilized to uniquely identify the mobile device and the risk index isutilized to manage the mobile device.
 10. The mobile device of claim 9,wherein the collected data includes any of device information, securitytelemetry, operating system upgrades, geolocation changes, applicationchanges, anti-virus status, device configuration, and combinationsthereof.
 11. The mobile device of claim 9, wherein the cloud-basedsystem utilizes the device fingerprint to authorize a user and fortracking the user in all network access attempts.
 12. The mobile deviceof claim 9, wherein the device fingerprint is a combination of postureinformation from the collected data and is represent as a hash of theposture information.
 13. The mobile device of claim 9, wherein the riskindex is utilized for access to or through the cloud-based system. 14.The mobile device of claim 9, wherein the risk index is based on acombination of user browsing pattern, device risk, application risk,resource risk, user risk, and environment risk.
 15. The mobile device ofclaim 9, wherein the risk index is continually updated.
 16. The mobiledevice of claim 9, wherein the memory storing computer executableinstructions, and in response to execution by the processor, thecomputer-executable instructions cause the processor to provide a userrequest to resources in or through the cloud-based system, wherein theuser request is one of allowed, quarantined, or denied by thecloud-based system based on the risk index.
 17. A non-transitorycomputer-readable medium comprising computer executable instructions,and in response to execution by the processor, the computer-executableinstructions cause the processor to based on communication to a clientapplication on the mobile device, cause the client application tocollect data associated with the mobile device; receive the collecteddata; and determine a device fingerprint and a risk index for the mobiledevice based on the collected data, wherein the device fingerprint isutilized to uniquely identify the mobile device and the risk index isutilized to manage the mobile device.
 18. The non-transitorycomputer-readable medium of claim 1, wherein the collected data includesany of device information, security telemetry, operating systemupgrades, geolocation changes, application changes, anti-virus status,device configuration, and combinations thereof.
 19. The non-transitorycomputer-readable medium of claim 17, wherein the risk index is utilizedfor access to or through the cloud-based system.
 20. The non-transitorycomputer-readable medium of claim 17, wherein, in response to executionby the processor, the computer-executable instructions cause theprocessor to one of allow, quarantine, or deny a user request toresources in or through the cloud-based system based on the risk index.